https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #13 from GCC Commits ---
The master branch has been updated by Tamar Christina :
https://gcc.gnu.org/g:c8c587b854c9e85fc9ce58c8192d532205f0ee1f
commit r14-9104-gc8c587b854c9e85fc9ce58c8192d532205f0ee1f
Author: Tamar Christina
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
Tamar Christina changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2022-09-28 00:00:00 |2023-11-23
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #10 from Richard Earnshaw ---
That sounds broadly sensible. One optimization might be to check if the
exception trapping is already enabled, then you can skip the read/set/restore
dance entirely in that case. That might be more effi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #9 from Francois-Xavier Coudert ---
OK so there are three things tested here:
- underflow mode
- rounding mode
- trapping mode
For glibc targets, underflow control is only marked as supported for the float
and double types on __alp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #8 from Richard Earnshaw ---
(In reply to Francois-Xavier Coudert from comment #7)
> @Richard The test in gfortran.dg/ieee/modes_1.f90 is not doing that. It is
> checking that the floating-point modes (rounding mode, underflow mode,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #7 from Francois-Xavier Coudert ---
@Richard The test in gfortran.dg/ieee/modes_1.f90 is not doing that. It is
checking that the floating-point modes (rounding mode, underflow mode, and
halting modes) can be set and restored. It is n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #6 from Richard Earnshaw ---
Whilst the patch is probably fine and a better way of doing this, it won't fix
the test failure. I think your problem is that you're assuming that an
exception will cause a trap in hardware. That's not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #5 from Francois-Xavier Coudert ---
Right now the code to test support is indeed like this for glibc targets except
x86/x86_64 (libgfortran/config/fpu-glibc.h):
int
support_fpu_rounding_mode (int mode)
{
switch (mode)
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #4 from Andreas Schwab ---
The problem is that set_fpu_trap_exceptions does not check if feenableexcept
was successful. Just because FE_* are defined does not mean that the hardware
supports fpu exceptions of that kind (it may depen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #3 from Andreas Schwab ---
Still STOP 3.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
Francois-Xavier Coudert changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107071
--- Comment #1 from Andreas Schwab ---
STOP 3
13 matches
Mail list logo
