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 ipa/113665] [11/12/13/14 regression] Regular for Loop results in Endless Loop with -O2
Date: Tue, 30 Jan 2024 08:16:31 +0000	[thread overview]
Message-ID: <bug-113665-4-xGtpvGv0G5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113665-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113665

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org,
                   |                            |rguenth at gcc dot gnu.org
           Priority|P3                          |P2

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Honza - ICF seems to fixup points-to sets when merging variables, so there
should be a way to kill off flow-sensitive info inside prevailing bodies
as well.  But would that happen before inlining the body?  Can you work
on that?  I think comparing ranges would weaken ICF unnecessarily?

  parent reply	other threads:[~2024-01-30  8:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 23:11 [Bug c++/113665] New: " christoph at muppetnet dot net
2024-01-29 23:14 ` [Bug c++/113665] " christoph at muppetnet dot net
2024-01-30  0:25 ` [Bug ipa/113665] " pinskia at gcc dot gnu.org
2024-01-30  6:01 ` [Bug ipa/113665] [11/12/13/14 regression] " sjames at gcc dot gnu.org
2024-01-30  6:04 ` pinskia at gcc dot gnu.org
2024-01-30  8:11 ` rguenth at gcc dot gnu.org
2024-01-30  8:16 ` rguenth at gcc dot gnu.org [this message]
2024-01-30  9:12 ` [Bug ipa/113665] [11/12/13/14 regression] Regular for Loop results in Endless Loop with -O2 since r11-4987-g602c6cfc79ce4a sjames at gcc dot gnu.org
2024-01-30 17:21 ` hubicka at ucw dot cz
2024-01-31  7:35 ` rguenth at gcc dot gnu.org
2024-03-09 17:10 ` law 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-113665-4-xGtpvGv0G5@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).