Changeset 4170


Ignore:
Timestamp:
Apr 10, 2006, 4:20:30 PM (15 years ago)
Author:
gb
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/ccl/ChangeLog

    r4163 r4170  
     12006-04-10 10:19  gb
     2
     3        * lisp-kernel/x86-spentry64.s: _SPcallback is now called with the
     4        foreign SP properly obeying C alignment conventions.  In order to
     5        get it aligned for lisp usage during the callback, an extra word
     6        needs to be pushed before the backpointer to the old foreign RSP.
     7
     82006-04-10 10:18  gb
     9
     10        * lisp-kernel/x86-exceptions.c: Ensure that the copied sigcontext
     11        is 16-byte aligned, so that the foreign stack pointer is aligned
     12        according to C conventions when we enter the signal handler on that
     13        stack.
     14
     152006-04-10 10:13  gb
     16
     17        * lib/numbers.lisp: Define FP infinities, since we're running with
     18        FP exceptions masked. (We don't handle FP exceptions on X8664 yet,
     19        but this was crashing due to ldmxcsr/stmxcsr confusion, not because
     20        an unmasked FP exception was raised and unhandled.)
     21
     222006-04-10 10:10  gb
     23
     24        * lib/level-2.lisp: Remove the WARN and the conditionalization
     25        around bit/bitfield accessors on X8664.
     26
     272006-04-10 10:09  gb
     28
     29        * level-0/X86/x86-float.lisp: Repeat after me: to load the mxcsr
     30        from memory, we say "ldmxcsr".  We want to do such a load in order
     31        to write new values into the mxcsr.  To store it in memory, we say
     32        "stmxcsr".  We want to do such a store (and a subsequent load from
     33        memory) in order to access the value of the mxcsr.  Simple, no ?
     34
     352006-04-10 10:07  gb
     36
     37        * compiler/X86/: x862.lisp, X8664/x8664-vinsns.lisp:
     38        %GET-BIT/%SET-BIT.
     39
    1402006-04-10 08:29  gb
    241
Note: See TracChangeset for help on using the changeset viewer.