Mirrors_Framework/rtems
1
0
Fork 0
mirror of https://gitlab.rtems.org/rtems/rtos/rtems.git synced 2026-08-31 13:38:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

2006-08-09 Joel Sherrill <joel@OARcorp.com>

Browse Source 
* rtems/score/cpu.h: Because gcc implicitly uses floating point turn on
	floating point for all threads if there is a hardware FPU.
This commit is contained in:
Joel Sherrill
2006-08-09 23:04:47 +00:00
parent 417fca7663
commit a19034d902
2 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cpukit/score/cpu/powerpc/ChangeLog
+5
View File
@@ -1,3 +1,8 @@
2006-08-09 Joel Sherrill <joel@OARcorp.com>
* rtems/score/cpu.h: Because gcc implicitly uses floating point turn on
floating point for all threads if there is a hardware FPU.
2006-07-12 Till Straumann <strauman@slac.stanford.edu>
* rtems/old-exceptions/cpu.h, rtems/powerpc/registers.h:
cpukit/score/cpu/powerpc/rtems/score/cpu.h
+5 -1
View File
@@ -157,9 +157,13 @@
* If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed.
*
* If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well.
*
* PowerPC Note: It appears the GCC can implicitly generate FPU
* and Altivec instructions when you least expect them. So make
* all tasks floating point.
*/
#define CPU_ALL_TASKS_ARE_FP FALSE
#define CPU_ALL_TASKS_ARE_FP CPU_HARDWARE_FP
/*
* Should the IDLE task have a floating point context?