Why is -msoft-float used in Kernel compilation?
I can understand using -msoft-float if CONFIG__8xx is on, but why use it when compiling for 60x or 7x0 CPUs?
-Gav
--
Gavriel State
Engineering Project Leader - Linux Apps
Corel Corp
[email protected]
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]] [[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]] [[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]] [[ the message 'unsubscribe' to [email protected] ]]
Quoted 3 lines · Gavriel State
I can understand using -msoft-float if
CONFIG__8xxis on, but why use it when compiling for 60x or 7x0 CPUs?
I would imagine to prevent the compiler from using the FPU to move 64-bit aligned items via fp registers.
Signature · 8 lines
Michael Meissner, Cygnus Solutions (Massachusetts office) 4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA [email protected], 617-354-5416 (office), 617-354-7161 (fax) [[ This message was sent via the linuxppc-dev mailing list. Replies are ]] [[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]] [[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]] [[ the message 'unsubscribe' to [email protected] ]]
On 13 Feb, this message from Gavriel State echoed through cyberspace:
Quoted 3 lines
I can understand using -msoft-float if
CONFIG__8xxis on, but why use it when compiling for 60x or 7x0 CPUs?
I've heard something about a 'no floiting point in kernel' rule, and I've tried compiling without -msoft-float.... it does boot, but it's an ugly sight... fp warning messages all over!
I have, however, never seen a clear explanation of why that rule exists...
Any guru around?
Michel
-------------------------------------------------------------------------
Michel Lanners | " Read Philosophy. Study Art. 23, Rue Paul Henkes | Ask Questions. Make Mistakes. L-1710 Luxembourg | email [email protected] | http://www.cpu.lu/~mlan | Learn Always. "
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]] [[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]] [[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]] [[ the message 'unsubscribe' to [email protected] ]]
Quoted 6 lines · Michel Lanners
On 13 Feb, this message from Gavriel State echoed through cyberspace:
Quoted 3 lines
I can understand using -msoft-float if
CONFIG__8xxis on, but why use it when compiling for 60x or 7x0 CPUs?
Quoted 6 lines
I've heard something about a 'no floiting point in kernel' rule, and I've tried compiling without -msoft-float.... it does boot, but it's an ugly sight... fp warning messages all over!
I have, however, never seen a clear explanation of why that rule exists...
I'm not sure, but I believe it's an optimization to allow the kernel to not have to save floating point registers on every context switch.
--------------------------------------------------------------------------
| Troy Benjegerdes | [email protected] | [email protected] | | Unix is user friendly... You just have to be friendly to it first. | | This message composed with 100% free software. http://www.gnu.org |
--------------------------------------------------------------------------
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]] [[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]] [[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]] [[ the message 'unsubscribe' to [email protected] ]]
Quoted 13 lines · On 15-Feb-99 Troy Benjegerdes wrote:
Quoted 10 lines · Michel Lanners
On 13 Feb, this message from Gavriel State echoed through cyberspace:
Quoted 3 lines
I can understand using -msoft-float if
CONFIG__8xxis on, but why use it when compiling for 60x or 7x0 CPUs?I've heard something about a 'no floiting point in kernel' rule, and I've tried compiling without -msoft-float.... it does boot, but it's an ugly sight... fp warning messages all over!
Quoted 6 lines
Quoted 2 lines
I have, however, never seen a clear explanation of why that rule exists...
I'm not sure, but I believe it's an optimization to allow the kernel to not have to save floating point registers on every context switch.
More importantly it is to keep GCC from trying to use FP registers to do structure copies. Without this option, GCC will try to use the FP registers to perform high[er] performance copying of structures. This would mean that the kernel would have to save/restore some number of FP registers on every context change, not just the switch from user to kernel mode, because these registers are considered totally volatile by the compiler.
------------------------------------------------------------------------
Gary Thomas | email: [email protected] | "Fine wine is a necessity of ... opinions expressed here are mine | life for me" and no one else would claim them! | | Thomas Jefferson
------------------------------------------------------------------------
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]] [[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]] [[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]] [[ the message 'unsubscribe' to [email protected] ]]