On Fri, 18 Jan 2013, Michael Zolotukhin wrote: > Sure, the tests are of utmost importance here. By the way, in what > suite should they be?
I suspect that things such as testing for both -mfpmath=387 and -mfpmath=sse indicate a new .exp file. That may also help for other things such as running tests using the same source files for (pragma FENV_ACCESS, -f options, ...), (volatile or non-volatile), and other such variations over which the tests should be iterated. Given that a new .exp file is used, it probably goes in a subdirectory of gcc.dg, e.g. gcc.dg/ieee/ieee.exp. > As for the changes in the compiler itself - what do you think about > introduction of a fake variable, reflecting rounding mode (similar > variables could be introduced for exception flags and other > properties). How difficult would it be to do that (we'll need to add > implicit dependencies from those variables to all FP-operations and > kill their values after each call)? I have no comments on this as an implementation approach (but thread-local variables, read and modified by various operations and function calls, are essentially what rounding mode and exception state are in C language terms). -- Joseph S. Myers jos...@codesourcery.com
