public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at redhat dot com" <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: Fri, 28 May 2021 18:02:32 +0000 [thread overview]
Message-ID: <bug-100787-4-dHMhReo6Fx@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 #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Perhaps if EVRP is folding debug stmts it could first fold non-debug stmts (and
remember if there were any debug stmts) and only fold debug stmts afterwards,
either just by using caches and not adding anything to them (if they survive to
later passes), or just to make sure that the debug stmts don't affect non-debug
folding.
--- Comment #8 from Aldy Hernandez <aldyh at redhat dot com> ---
I'll work on it this weekend. If there's no patch by Monday morning, we can
revert the patch while I find a solution.
On Fri, May 28, 2021, 19:49 ro at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100787
>
> Rainer Orth <ro at gcc dot gnu.org> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> Target|i686 |i686, sparc
> CC| |ro at gcc dot gnu.org
>
> --- Comment #6 from Rainer Orth <ro at gcc dot gnu.org> ---
> It also affects 32-bit sparc (sparc-sun-solaris2.11), maybe other 32-bit
> targets, too? Unless a quick fix is coming forward, I suspect it would be
> better
> to revert the patch instead of keeping bootstrap broken for days.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
> You are on the CC list for the bug.
>
>
next prev parent reply other threads:[~2021-05-28 18:02 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 [this message]
2021-05-28 20:51 ` aldyh at gcc dot gnu.org
2021-05-29 5:45 ` cvs-commit at gcc dot gnu.org
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-dHMhReo6Fx@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).