Custom Query (1030 matches)
Results (385 - 387 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #620 | fixed | Type assertions in parse tree confuse at least a few things in compiler backends | ||
| Description |
http://clozure.com/pipermail/openmcl-devel/2009-October/010673.html describes one example of this. |
|||
| #621 | fixed | THE chokes on VALUES type specifiers | ||
| Description |
http://clozure.com/pipermail/openmcl-devel/2009-October/010672.html |
|||
| #624 | fixed | relocate_area_contents() and "large" x8632 functions | ||
| Description |
We made a change to support "large" functions (those with 64K or more 32-bit words of code/immediate data) on x8632 by changing the interpretation of the 16-bit word which precedes the function entry point (high bit clear -> count of "code" words in low 15 bits, high bit set -> count of "node" words in low 15 bits.) We missed a case in relocate_area_contents(), which is used to handle the case where a heap image can't be mapped into the address from which it was saved. A development version of ACL2 both created at least one "large" function and was saved from a non-canonical address (for unknown reasons) and exposed this problem. |
|||
