* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
@ 2023-10-05 17:50 ` danglin at gcc dot gnu.org
2023-10-05 17:51 ` danglin at gcc dot gnu.org
` (13 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-05 17:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #1 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 56057
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56057&action=edit
Preprocessed source generated using gcc-13
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
2023-10-05 17:50 ` [Bug regression/111709] " danglin at gcc dot gnu.org
@ 2023-10-05 17:51 ` danglin at gcc dot gnu.org
2023-10-05 17:52 ` danglin at gcc dot gnu.org
` (12 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-05 17:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #2 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 56058
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56058&action=edit
.s file for s_fma.c generated using gcc-12
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
2023-10-05 17:50 ` [Bug regression/111709] " danglin at gcc dot gnu.org
2023-10-05 17:51 ` danglin at gcc dot gnu.org
@ 2023-10-05 17:52 ` danglin at gcc dot gnu.org
2023-10-05 18:01 ` danglin at gcc dot gnu.org
` (11 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-05 17:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #3 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 56059
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56059&action=edit
.s file for s_fma.c generated using gcc-13
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (2 preceding siblings ...)
2023-10-05 17:52 ` danglin at gcc dot gnu.org
@ 2023-10-05 18:01 ` danglin at gcc dot gnu.org
2023-10-05 18:01 ` danglin at gcc dot gnu.org
` (10 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-05 18:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #4 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 56060
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56060&action=edit
non pic .s file for s_fma.c generated using gcc-12 without debug info
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (3 preceding siblings ...)
2023-10-05 18:01 ` danglin at gcc dot gnu.org
@ 2023-10-05 18:01 ` danglin at gcc dot gnu.org
2023-10-05 18:06 ` danglin at gcc dot gnu.org
` (9 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-05 18:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #5 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 56061
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56061&action=edit
non pic .s file for s_fma.c generated using gcc-13 without debug info
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (4 preceding siblings ...)
2023-10-05 18:01 ` danglin at gcc dot gnu.org
@ 2023-10-05 18:06 ` danglin at gcc dot gnu.org
2023-10-05 18:25 ` danglin at gcc dot gnu.org
` (8 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-05 18:06 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #6 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 56062
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56062&action=edit
Diff between s_fma_12.s and s_fma_13.s
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (5 preceding siblings ...)
2023-10-05 18:06 ` danglin at gcc dot gnu.org
@ 2023-10-05 18:25 ` danglin at gcc dot gnu.org
2023-10-05 20:33 ` joseph at codesourcery dot com
` (7 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-05 18:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jsm28 at gcc dot gnu.org
--- Comment #7 from John David Anglin <danglin at gcc dot gnu.org> ---
Joseph, is there a way to simplify the glibc test to the failing cases?
Maybe you have a clue as to what has changed.
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (6 preceding siblings ...)
2023-10-05 18:25 ` danglin at gcc dot gnu.org
@ 2023-10-05 20:33 ` joseph at codesourcery dot com
2023-10-06 7:50 ` rguenth at gcc dot gnu.org
` (6 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: joseph at codesourcery dot com @ 2023-10-05 20:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Typically these sorts of issues result from floating-point operations
being moved past environment manipulation (fesetround, feupdateenv,
feholdexcept, etc.) - in either direction. This might be a compiler
issue, or it might well be a bug in the glibc function implementation
(insufficient use of math_opt_barrier / math_force_eval to prevent such
movement). If the latter, make sure to fix it in all similar
implementations of fma functions, not just the dbl-64 one.
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (7 preceding siblings ...)
2023-10-05 20:33 ` joseph at codesourcery dot com
@ 2023-10-06 7:50 ` rguenth at gcc dot gnu.org
2023-10-07 22:33 ` dave.anglin at bell dot net
` (5 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: rguenth at gcc dot gnu.org @ 2023-10-06 7:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |13.3
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Does it work on trunk?
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (8 preceding siblings ...)
2023-10-06 7:50 ` rguenth at gcc dot gnu.org
@ 2023-10-07 22:33 ` dave.anglin at bell dot net
2023-10-11 15:36 ` [Bug regression/111709] [13/14 " danglin at gcc dot gnu.org
` (4 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: dave.anglin at bell dot net @ 2023-10-07 22:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #10 from dave.anglin at bell dot net ---
On 2023-10-06 3:50 a.m., rguenth at gcc dot gnu.org wrote:
> Does it work on trunk?
No. Test results with gcc trunk are identical to with Debian gcc-13.
Tried just rebuilding s_fma.c, and a full build and check.
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13/14 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (9 preceding siblings ...)
2023-10-07 22:33 ` dave.anglin at bell dot net
@ 2023-10-11 15:36 ` danglin at gcc dot gnu.org
2023-10-15 1:15 ` danglin at gcc dot gnu.org
` (3 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-11 15:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #11 from John David Anglin <danglin at gcc dot gnu.org> ---
This is proving difficult to bisect due to _Floatn issues.
I know commit b85e79dce149df68b92ef63ca2a40ff1dfa61396 is good and
commit b939a5cc4143908ddda4b85a848c313136ff6e0c is bad.
The following glibc change breaks gcc build when BASE-VER changes to 13.
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=3e5760fcb48528d48deeb60cb885a97bb731160c
If I change __GNUC_PREREQ to 13, 1, I hit errors like:
In file included from
/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/incl
ude/cmath:45,
from
/home/dave/gnu/gcc/objdir/hppa-linux-gnu/libstdc++-v3/incl
ude/complex:44,
from
../../../../../gcc/libstdc++-v3/src/c++98/complex_io.cc:25
:
/usr/include/math.h:1395:19: error: redefinition of ‘struct
__iseqsig_type<float
>’
1395 | template<> struct __iseqsig_type<_Float32>
| ^~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/math.h:1366:19: note: previous definition of ‘struct
__iseqsig_type
<float>’
1366 | template<> struct __iseqsig_type<float>
There are a lot of VRP changes for floats in the range that I haven't been able
to bisect.
| ^~~~~~~~~~~~~~~~~~~~~
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13/14 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (10 preceding siblings ...)
2023-10-11 15:36 ` [Bug regression/111709] [13/14 " danglin at gcc dot gnu.org
@ 2023-10-15 1:15 ` danglin at gcc dot gnu.org
2024-05-02 3:04 ` [Bug regression/111709] [13/14/15 " matoro_gcc_bugzilla at matoro dot tk
` (2 subsequent siblings)
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2023-10-15 1:15 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aldyh at redhat dot com,
| |jeffreyalaw at gmail dot com
--- Comment #12 from John David Anglin <danglin at gcc dot gnu.org> ---
The miscompilation of s_fma.c was introduced by the following change:
dave@atlas:~/gnu/gcc/gcc$ git bisect good
8c99e307b20c502e55c425897fb3884ba8f05882 is the first bad commit
commit 8c99e307b20c502e55c425897fb3884ba8f05882
Author: Aldy Hernandez <aldyh@redhat.com>
Date: Sat Jun 25 18:58:02 2022 -0400
Convert DOM to use Ranger rather than EVRP
[Jeff, this is the same patch I sent you last week with minor tweaks
to the commit message.]
[Despite the verbosity of the message, this is actually a pretty
straightforward patch. It should've gone in last cycle, but there
was a nagging regression I couldn't get to until after stage1
had closed.]
There are 3 uses of EVRP in DOM that must be converted.
Unfortunately, they need to be converted in one go, so further
splitting of this patch would be problematic.
There's nothing here earth shattering. It's all pretty obvious in
retrospect, but I've added a short description of each use to aid in
reviewing:
* Convert evrp use in cprop to ranger.
This is easy, as cprop in DOM was converted to the ranger API last
cycle, so this is just a matter of using a ranger instead of an
evrp_range_analyzer.
* Convert evrp use in threader to ranger.
The idea here is to use the hybrid approach we used for the initial
VRP threader conversion last cycle. The DOM threader will continue
using the forward threader infrastructure while continuing to query
DOM data structures, and only if the conditional does not relsolve,
using the ranger. This gives us the best of both worlds, and is a
proven approach.
Furthermore, as frange and prange come live in the next cycle, we
can move away from the forward threader altogether, and just add
another backward threader. This will not only remove the last use
of the forward threader, but will allow us to remove at least 1 or 2
threader instances.
* Convert conditional folding to use the method used by the ranger and
evrp. Previously DOM was calling into the guts of
simplify_using_ranges::vrp_visit_cond_stmt. The blessed way now is
using fold_cond() which rewrites the conditional and edges
automatically.
When legacy is removed, simplify_using_ranges will be further
cleaned up, and there will only be one entry point into simplifying
a statement.
* DOM was setting global ranges determined from unreachable edges as a
side-effect of using the evrp engine. We must handle these cases
before nuking evrp, and DOM seems like a good fit. I've just moved
the snippet to DOM, but it could live anywhere else we do a DOM
walk.
For the record, this is the case *vrp handled:
<bb C>:
...
if (c_5(D) != 5)
goto <bb N>;
else
goto <bb M>;
<bb N>:
__builtin_unreachable ();
<bb M>:
If M dominates all uses of c_5, we can set the global range of c_5
to [5,5].
I have tested on x86-64, pcc64le, and aarch64 Linux.
I also ran threading benchmarks as well as performance benchmarks.
DOM threads 1.56% more paths which ultimately yields a miniscule total
increase of 0.03%.
The conversion to ranger brings a 7.87% performance drop in DOM, which
is a wash in overall compilation. This is in line with other
replacements of legacy evrp with ranger. We handle a lot more cases.
It's not free .
There is a a regression on Wstringop-overflow-4.C which I'm planning
on XFAILing. It's another variant of the usual middle-end false
positives: having no ranges produces no warnings, but slightly refined
ranges, or worse-- isolating specific problematic cases in the
threader causes flare-ups.
As an aside, as Richi has suggested, I think we should discuss
restricting the threader's ability to thread highly unlikely paths.
These cause no end of pain for middle-end warnings. However,
I don't know if this would conflict with path isolation for
things like null dereferencing. ISTR you were interested in this.
BTW, I think the Wstringop-overflow-4.C test is problematic and I've
attached my analysis. Basically the regression is caused by a bad
interaction with the rounding/alignment that placement new has inlined
into the IL. This happens for int16_r[] which the test is testing.
Ranger can glean some range info, which causes DOM threading to
isolate a path which causes a warning.
OK for trunk?
gcc/ChangeLog:
* tree-ssa-dom.cc (dom_jt_state): Pass ranger to constructor
instead of evrp.
(dom_jt_state::push): Remove m_evrp.
(dom_jt_state::pop): Same.
(dom_jt_state::record_ranges_from_stmt): Remove.
(dom_jt_state::register_equiv): Remove updating of evrp ranges.
(class dom_jt_simplifier): Pass ranger to constructor.
Inherit from hybrid_jt_simplifier.
(dom_jt_simplifier::simplify): Convert to ranger.
(pass_dominator::execute): Same.
(all_uses_feed_or_dominated_by_stmt): New.
(dom_opt_dom_walker::set_global_ranges_from_unreachable_edges):
New.
(dom_opt_dom_walker::before_dom_children): Call
set_global_ranges_from_unreachable_edges.
Do not call record_ranges_from_stmt.
(dom_opt_dom_walker::after_dom_children): Remove evrp use.
(cprop_operand): Use int_range<> instead of value_range.
(dom_opt_dom_walker::fold_cond): New.
(dom_opt_dom_walker::optimize_stmt): Pass ranger to
cprop_into_stmt.
Use fold_cond() instead of vrp_visit_cond_stmt().
* tree-ssa-threadedge.cc (jt_state::register_equivs_stmt): Do not
pass state to simplifier.
* vr-values.h (class vr_values): Make fold_cond public.
gcc/testsuite/ChangeLog:
* gcc.dg/sancov/cmp0.c: Adjust for conversion to ranger.
* gcc.dg/tree-ssa/ssa-dom-branch-1.c: Same.
* gcc.dg/tree-ssa/ssa-dom-thread-7.c: Same.
* gcc.dg/vect/bb-slp-pr81635-2.c: Same.
* gcc.dg/vect/bb-slp-pr81635-4.c: Same.
* g++.dg/warn/Wstringop-overflow-4.C: Likewise.
* gcc.target/mips/data-sym-multi-pool.c: Likewise.
* gcc.target/mips/mips.exp: Likewise.
gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C | 34 ++++
gcc/testsuite/gcc.dg/sancov/cmp0.c | 2 +-
gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-branch-1.c | 5 +-
gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-7.c | 2 +-
gcc/testsuite/gcc.dg/vect/bb-slp-pr81635-2.c | 2 +-
gcc/testsuite/gcc.dg/vect/bb-slp-pr81635-4.c | 6 +-
.../gcc.target/mips/data-sym-multi-pool.c | 2 +-
gcc/testsuite/gcc.target/mips/mips.exp | 1 +
gcc/tree-ssa-dom.cc | 223 +++++++++++----------
gcc/tree-ssa-threadedge.cc | 4 +-
gcc/vr-values.h | 2 +-
11 files changed, 170 insertions(+), 113 deletions(-)
I don't know anything about ranger but I wonder if this has to do with
the mips/hppa NaN representation.
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13/14/15 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (11 preceding siblings ...)
2023-10-15 1:15 ` danglin at gcc dot gnu.org
@ 2024-05-02 3:04 ` matoro_gcc_bugzilla at matoro dot tk
2024-05-02 15:28 ` danglin at gcc dot gnu.org
2024-05-21 9:18 ` jakub at gcc dot gnu.org
14 siblings, 0 replies; 16+ messages in thread
From: matoro_gcc_bugzilla at matoro dot tk @ 2024-05-02 3:04 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
--- Comment #13 from matoro <matoro_gcc_bugzilla at matoro dot tk> ---
Current state of this has expanded to more of the math tests.
FAIL: math/test-double-fma
FAIL: math/test-double-j0
FAIL: math/test-double-j1
FAIL: math/test-double-ldouble-fma
FAIL: math/test-double-log
FAIL: math/test-float32x-float64-fma
FAIL: math/test-float32x-fma
FAIL: math/test-float32x-j0
FAIL: math/test-float32x-j1
FAIL: math/test-float32x-log
FAIL: math/test-float64-fma
FAIL: math/test-float64-j0
FAIL: math/test-float64-j1
FAIL: math/test-float64-log
FAIL: math/test-ldouble-fma
FAIL: math/test-ldouble-j0
FAIL: math/test-ldouble-j1
FAIL: math/test-ldouble-log
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13/14/15 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (12 preceding siblings ...)
2024-05-02 3:04 ` [Bug regression/111709] [13/14/15 " matoro_gcc_bugzilla at matoro dot tk
@ 2024-05-02 15:28 ` danglin at gcc dot gnu.org
2024-05-21 9:18 ` jakub at gcc dot gnu.org
14 siblings, 0 replies; 16+ messages in thread
From: danglin at gcc dot gnu.org @ 2024-05-02 15:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2024-05-02
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
^ permalink raw reply [flat|nested] 16+ messages in thread* [Bug regression/111709] [13/14/15 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
2023-10-05 17:49 [Bug regression/111709] New: [13 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c danglin at gcc dot gnu.org
` (13 preceding siblings ...)
2024-05-02 15:28 ` danglin at gcc dot gnu.org
@ 2024-05-21 9:18 ` jakub at gcc dot gnu.org
14 siblings, 0 replies; 16+ messages in thread
From: jakub at gcc dot gnu.org @ 2024-05-21 9:18 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111709
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|13.3 |13.4
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
GCC 13.3 is being released, retargeting bugs to GCC 13.4.
^ permalink raw reply [flat|nested] 16+ messages in thread