Custom Query (1030 matches)
Results (295 - 297 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #837 | fixed | Some constant-valued integer expressions can be evaluated twice in generated code | ||
| Description |
From Eric Marsden on openmcl-devel: | Welcome to Clozure Common Lisp Version 1.7-dev-r14686M (LinuxX8664)! | ? (defun foo () | (catch 'ct5 (throw 'ct5 (logior -920833 (the integer -2513842743151))))) | FOO | ? (foo) | > Error: Can't throw to tag -263425 | > While executing: FOO, in process listener(1). `---- |
|||
| #855 | fixed | ARM port pc-lusering fails to recognize allocation sequence | ||
| Description |
Running the simple test case from ticket:717 results in a trip to the kernel debugger with the complaint: unexpected instruction preceding alloc trap. The unexpected instruction is the (relatively new) branch around an unconditional uuo_alloc_trap. If pc_luser_xp() notes that a thread is at the alloc_trap, it expects the immediately preceding instruction to be a comparison, and that's now an instruction earlier. |
|||
| #857 | fixed | ARM fp register tracking | ||
| Description |
The ARM fp unit generally offers at least 32 single-float registers (s0-s31) and at least 16 double-float registers (d0-d15); modern VFP implementations offer more than 16 doubles. s0 and s1 occupy the same 64 bits in a 128-bit vector register as does d0, s2 and s3 conflict with d1, etc. The compiler thinks that (for instance) s1 and d0 are disjoint and thus (at least in theory) might try to keep distinct live values in conflicting FPRs. |
|||
