public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100787] [12 Regression] Bootstrap failure caused by r12-1077
Date: Sat, 29 May 2021 05:45:33 +0000 [thread overview]
Message-ID: <bug-100787-4-3gwW92KISW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100787-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100787
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>:
https://gcc.gnu.org/g:2364b584552208ce715fa4fd44c510b7e5210d1e
commit r12-1118-g2364b584552208ce715fa4fd44c510b7e5210d1e
Author: Aldy Hernandez <aldyh@redhat.com>
Date: Fri May 28 22:17:51 2021 +0200
Fix i686 bootstrap by temporarily disabling exporting of global ranges.
The patch converting evrp to the get_range_query(fun) API broke i686
bootstrap (commit 57bf37515). The problem seems to be in a subsequent
pass that has more up-to-date global ranges. I won't be able to look at
this until next week, so I am reverting the problematic bit of the
patch-- the exporting of global ranges once evrp finishes. The use of
the new API remains.
Reverting the behavior shouldn't be a problem as we never used to export
global ranges from ranger. This was new behavior in the patchset.
Tested on x86-64 Linux with a bootstrap and regtest, and on x86-32 with
only a bootstrap and the configure flags from the PR:
--enable-clocale=gnu --with-system-zlib --with-demangler-in-ld
--with-fpmath=sse --enable-languages=c,c++ --enable-cet i686-linux
--enable-bootstrap --with-fpmath=sse --disable-libcc1 --disable-libcilkrts
--disable-libsanitizer
gcc/ChangeLog:
PR tree-optimization/100787
* gimple-ssa-evrp.c: Disable exporting of global ranges.
gcc/testsuite/ChangeLog:
* gcc.dg/Wstringop-overflow-55.c:
* gcc.dg/pr80776-1.c:
next prev parent reply other threads:[~2021-05-29 5:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 2:32 [Bug bootstrap/100787] New: " hjl.tools at gmail dot com
2021-05-27 3:25 ` [Bug middle-end/100787] " pinskia at gcc dot gnu.org
2021-05-27 6:55 ` [Bug tree-optimization/100787] " aldyh at gcc dot gnu.org
2021-05-27 7:21 ` jakub at gcc dot gnu.org
2021-05-27 11:38 ` aldyh at gcc dot gnu.org
2021-05-27 11:52 ` hjl.tools at gmail dot com
2021-05-28 10:35 ` rguenth at gcc dot gnu.org
2021-05-28 17:49 ` ro at gcc dot gnu.org
2021-05-28 18:02 ` jakub at gcc dot gnu.org
2021-05-28 18:02 ` aldyh at redhat dot com
2021-05-28 20:51 ` aldyh at gcc dot gnu.org
2021-05-29 5:45 ` cvs-commit at gcc dot gnu.org [this message]
2021-05-29 5:50 ` aldyh at gcc dot gnu.org
2021-05-29 21:39 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-06-01 15:00 ` aldyh 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-100787-4-3gwW92KISW@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).