https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103491
--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- This testcase is incorrect. This call to nextafter has a finite result, so it's correct that no exceptions are raised and so an exit status of 1 from the provided testcase is what should be expected. A GCC bug could only be demonstrated if the call were elided for arguments for which overflow or underflow occurs (such as (DBL_MAX, INFINITY) or (DBL_MIN, 0) or (DBL_TRUE_MIN, 0)). I haven't tested whether that is the case.
