From: Joseph Myers <joseph@codesourcery.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>,
Martin Sebor <msebor@redhat.com>,
libc-alpha@sourceware.org
Subject: Re: Failures building glibc with mainline GCC
Date: Fri, 30 Jul 2021 20:52:17 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2107302051370.581212@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAGm3qMURZ-m37CpxAdkvao3Y3KbKPTmV0HYgFhsuMrkZJ17CbQ@mail.gmail.com>
On Fri, 30 Jul 2021, Aldy Hernandez via Gcc wrote:
> There's a new jump threader in GCC which is much more aggressive, and
> may trigger latent problems with other warning passes, especially
> -Warray-bounds, -Woverflow, and -Wuninitialized.
>
> Do your problems go away if you take out commit 2e96b5f14e?
Reverting that commit fixes all the glibc build failures except for
x86_64-linux-gnu, i686-gnu and powerpc64le-linux-gnu.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-07-30 20:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 15:30 Failures building glibc with mainline GCC Joseph Myers
2021-07-30 16:19 ` Aldy Hernandez via Libc-alpha
2021-07-30 16:22 ` Jeff Law via Libc-alpha
2021-07-30 16:45 ` Jeff Law via Libc-alpha
2021-07-30 17:28 ` Martin Sebor via Libc-alpha
2021-07-30 20:52 ` Joseph Myers [this message]
2021-08-02 20:20 ` Martin Sebor via Libc-alpha
2021-08-03 15:54 ` Joseph Myers
2021-08-03 16:20 ` Martin Sebor via Libc-alpha
2021-08-03 17:21 ` Joseph Myers
2021-08-03 17:39 ` Samuel Thibault via Libc-alpha
2021-08-03 22:33 ` Martin Sebor via Libc-alpha
2021-08-03 20:50 ` Segher Boessenkool
2021-08-03 21:00 ` Joseph Myers
2021-08-03 22:02 ` Segher Boessenkool
2021-08-03 22:59 ` Martin Sebor via Libc-alpha
2021-07-30 16:38 ` Joseph Myers
2021-07-30 16:43 ` Jakub Jelinek via Libc-alpha
2021-07-30 16:53 ` Martin Sebor via Libc-alpha
2021-07-30 17:02 ` Jakub Jelinek via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2107302051370.581212@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=msebor@redhat.com \
/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).