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 tree-optimization/95045] [11 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Mon, 11 May 2020 08:01:24 +0000	[thread overview]
Message-ID: <bug-95045-4-04AT8ppfFG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95045-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
OK, this one is an interesting one (might be also latent before the rewrite). 
I'll deal with it separately.  The issue is around the inner loop having
multiple exits, one being also the exit from the outer loop and edge
inserts on that edge getting mis-ordered (we commit them only after processing
all inserts).

  parent reply	other threads:[~2020-05-11  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11  5:11 [Bug tree-optimization/95045] New: " qrzhang at gatech dot edu
2020-05-11  6:55 ` [Bug tree-optimization/95045] " rguenth at gcc dot gnu.org
2020-05-11  7:27 ` [Bug tree-optimization/95045] [11 Regression] " marxin at gcc dot gnu.org
2020-05-11  8:01 ` rguenth at gcc dot gnu.org [this message]
2020-05-12  6:22 ` cvs-commit at gcc dot gnu.org
2020-05-12  6:26 ` rguenth 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-95045-4-04AT8ppfFG@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).