public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109940] [14 Regression] ICE in decide_candidate_validity since g:53dddbfeb213ac4ec39f550aa81eaa4264375d2c
Date: Tue, 23 May 2023 15:52:59 +0000 [thread overview]
Message-ID: <bug-109940-4-Tmj7d0BP0z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109940-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109940
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
If that makes a difference then it should be because the compute_rd () dataflow
computes something different. The CFG is quite regular as well so I guess we
now hit a latent issue present before but not exposed with the other iteration
order (but the dataflow solution shouldn't depend on the iteration order).
Somebody familiar with the pass needs to sit down and analyze what goes wrong.
next prev parent reply other threads:[~2023-05-23 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 8:28 [Bug c/109940] New: ICE in decide_candidate_validity, bisected to peter.waller at arm dot com
2023-05-23 8:41 ` [Bug c/109940] [14 Regression] ICE in decide_candidate_validity, bisected ktkachov at gcc dot gnu.org
2023-05-23 8:44 ` [Bug rtl-optimization/109940] [13 Regression] ICE in decide_candidate_validity since g:53dddbfeb213ac4ec39f550aa81eaa4264375d2c tnfchris at gcc dot gnu.org
2023-05-23 15:52 ` rguenth at gcc dot gnu.org [this message]
2023-05-23 19:13 ` [Bug rtl-optimization/109940] [14 " rsandifo at gcc dot gnu.org
2023-05-24 8:53 ` cvs-commit at gcc dot gnu.org
2023-05-24 8:56 ` rsandifo at gcc dot gnu.org
2023-05-24 10:58 ` peter.waller at arm dot com
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-109940-4-Tmj7d0BP0z@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).