On Fri, 30 Sep 2016, James Greenhalgh wrote: > I've added two testcases which test that when this option, or a C standards > dialect, would restrict the range of values to {-1, 0, 1, 2}, those are > the only values we see. At this stage in the patch series this trivially > holds for all targets.
As noted in my comments on patch 6, the tests should check FLT_EVAL_METHOD from <float.h>, not the internal __FLT_EVAL_METHOD__ macro (and <float.h> will need to contain conditionals so that the -std=c11 -D__STDC_WANT_IEC_60559_TYPES_EXT__ case uses the new values when appropriate). -- Joseph S. Myers jos...@codesourcery.com