Changeset 48f89683 in rtems for c/src/exec/score/ChangeLog


Ignore:
Timestamp:
May 14, 2002, 5:45:36 PM (19 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
19131e97
Parents:
06549dcf
Message:

2001-05-14 Till Straumann <strauman@…>

  • src/threaddispatch.c, src/threadhandler.c: Per PR211 fix saving/restoring floating point context. The fpsave and fprestore routines are only used in a executing context which _is_ fp and hence has the FPU enabled. The current behavior required the FPU always to be on which is very dangerous if lazy context switching is used. [Joel Note: Some ports explicitly enabled the FPU in the FP save and restore routines to avoid this.]

The patch also makes sure (on powerpc only) that the FPU is disabled
for integer tasks. Note that this is crucial if deferred fp context
switching is used. Otherwise, fp context corruption may go undetected!
Also note that even tasks which merely push/pop FP registers to/from
the stack without modifying them still MUST be FP tasks - otherwise
(if lazy FP context switching is used), FP register corruption (of
other, FP, tasks may occur)!

Furthermore, (on PPC) by default, lazy FP context save/restore
is _disabled_.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • c/src/exec/score/ChangeLog

    r06549dcf r48f89683  
     12001-05-14      Till Straumann <strauman@slac.stanford.edu>
     2
     3        * src/threaddispatch.c, src/threadhandler.c: Per PR211 fix
     4        saving/restoring floating point context.  The fpsave and fprestore
     5        routines are only used in a executing context which _is_ fp and hence
     6        has the FPU enabled. The current behavior required the FPU always to
     7        be on which is very dangerous if lazy context switching is used. 
     8        [Joel Note: Some ports explicitly enabled the FPU in the FP save and
     9        restore routines to avoid this.]
     10
     11        The patch also makes sure (on powerpc only) that the FPU is disabled
     12        for integer tasks. Note that this is crucial if deferred fp context
     13        switching is used. Otherwise, fp context corruption may go undetected!
     14        Also note that even tasks which merely push/pop FP registers to/from
     15        the stack without modifying them still MUST be FP tasks - otherwise
     16        (if lazy FP context switching is used), FP register corruption (of
     17        other, FP, tasks may occur)!
     18
     19        Furthermore, (on PPC) by default, lazy FP context save/restore
     20        is _disabled_.
     21
    1222001-04-26      Joel Sherrill <joel@OARcorp.com>
    223
Note: See TracChangeset for help on using the changeset viewer.