aboutsummaryrefslogtreecommitdiff
path: root/libgomp/ChangeLog
diff options
context:
space:
mode:
authorHans-Peter Nilsson <hp@axis.com>2022-03-22 22:53:02 +0100
committerHans-Peter Nilsson <hp@axis.com>2022-03-22 22:53:02 +0100
commit5d2233f4033dfa37ad88dc2eab138524fe64242e (patch)
tree8edb19ba6ba74b6dc4332a27c4440fcfad8dce47 /libgomp/ChangeLog
parent4b7d9f8f51bd96d290aac230c71e501fcb6b21a6 (diff)
downloadgcc-5d2233f4033dfa37ad88dc2eab138524fe64242e.zip
gcc-5d2233f4033dfa37ad88dc2eab138524fe64242e.tar.gz
gcc-5d2233f4033dfa37ad88dc2eab138524fe64242e.tar.bz2
libstdc++-v3 testsuite: Call fesetround(FE_DOWNWARD) only if defined
Without this, for a typical soft-float target such as cris-elf, after commit r12-7676-g5a4e208022e704 you'll see, in libstdc++.log: ... FAIL: 20_util/from_chars/6.cc (test for excess errors) Excess errors: /home/hp/tmp/auto0321/gcc/libstdc++-v3/testsuite/20_util/from_chars/6.cc:33: error: 'FE_DOWNWARD' was not declared in this scope UNRESOLVED: 20_util/from_chars/6.cc compilation failed to produce executable ... It appears to be a side-effect of that commit changing the way __cpp_lib_to_chars is defined. (On the bright side, ./7.cc now passes since that commit.) TFM, specifically fenv(3), says that "Each of the macros FE_DIVBYZERO, FE_INEXACT, FE_INVALID, FE_OVERFLOW, FE_UNDERFLOW is defined when the implementation supports handling of the corresponding exception". A git-grep shows that this was the only place using a FE_ macro unconditionally. libstdc++-v3: * testsuite/20_util/from_chars/6.cc (test01) [FE_DOWNWARD]: Conditionalize call to fesetround.
Diffstat (limited to 'libgomp/ChangeLog')
0 files changed, 0 insertions, 0 deletions