https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91282
Tamar Christina <tnfchris at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |tnfchris at gcc dot gnu.org --- Comment #1 from Tamar Christina <tnfchris at gcc dot gnu.org> --- 32-bit x86 and m68k have a different FLT_EVAL_METHOD by default so I'll skip the test on them, but x86_64-*-*-* shouldn't be failing and I can't reproduce it locally. s390 seems to work but the testsuite adds `-ansi` to the test which for some reason changes flt_eval_method to FLT_EVAL_METHOD_PROMOTE_TO_DOUBLE which `excess_precision_type` to give a different answer. Yet the output of the test still uses floats. This seems like a target bug? I can't tell if it's by design or not so I can skip the test on this target too when `-ansi` if that's the expected result.