https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102017
--- Comment #1 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- There are a number of complications here: - What's the code size overhead? Even if the performance overhead is trivial, I suspect the additional code might be non-trivial on an m-profile device, so is there a simple way to choose not to link such support in when not needed/wanted? Perhaps it could be done by using some weak function calls for raising the exceptions and then only link the stub code in if there are calls to fe*(). - How would it work in a hybrid -mfloat-abi=soft + -mfloat-abi=softfp environment? See the point above again, especially if the float-env testing routines can get inlined.
