[Patch RFC] Modify excess precision logic to permit FLT_EVAL_METHOD=16

2016-09-06 Thread James Greenhalgh
Hi, ISO/IEC TS 18661-3 redefines FLT_EVAL_METHOD. In this patch I'm interested in updating the code in GCC to handle two of the changes. The redefinition of the meanings of {0, 1, 2}, and the meaning of "N" for the specific case of N=16. In ISO/IEC TS 18661-3, these are defined as so: 0

Re: [Patch RFC] Modify excess precision logic to permit FLT_EVAL_METHOD=16

2016-09-07 Thread Joseph Myers
On Tue, 6 Sep 2016, James Greenhalgh wrote: > In c-family/c-cppbuiltin.c I've updated cpp_iec_559_value such that also > allow setting __GEC_IEC_559 if FLT_EVAL_METHOD=16, and I've updated > c_cpp_builtins to handle the new value, and use the new enum names. I think the special cases in this patc

Re: [Patch RFC] Modify excess precision logic to permit FLT_EVAL_METHOD=16

2016-09-07 Thread Joseph Myers
On Wed, 7 Sep 2016, Joseph Myers wrote: > How about instead having more than one target macro / hook. One would > indicate that excess precision is used by insn patterns (and be set only > for i386 and m68k). Another would indicate the API-level excess precision Or, maybe there would be a si