public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/111709] [13/14 Regression] Miscompilation of sysdeps/ieee754/dbl-64/s_fma.c
Date: Wed, 11 Oct 2023 15:36:37 +0000 [thread overview]
Message-ID: <bug-111709-4-RFbLaqAUof@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111709-4@http.gcc.gnu.org/bugzilla/>
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.
| ^~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2023-10-11 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 17:49 [Bug regression/111709] New: [13 " 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
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
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
2023-10-11 15:36 ` danglin at gcc dot gnu.org [this message]
2023-10-15 1:15 ` [Bug regression/111709] [13/14 " danglin at gcc dot gnu.org
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111709-4-RFbLaqAUof@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).