Hi Joseph, > fixincludes is the right place for a fix for this issue. There is a > plausible case for having an architecture-independent > __FLT_EVAL_METHOD_<something>__ macro that takes only values defined by > C99 (regardless of -fpermitted-flt-eval-methods), rather than using the > new C23 values such as 16, but if you did have such a macro you'd still > need to fixinclude the system headers - it would just affect exactly what > change fixincludes makes to those headers (if there were such a macro, > fixincludes could change the headers to use it).
There is still a difference. If we define a new macro __FLT_EVAL_METHOD_OLDSTYLE__ (however it is named), it means we can make a more robust fixinclude, using that macro. If we fixinclude right now to handle the value of 16, then we might have to update the fixinclude for any new value that comes along in the future. FX
