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/101009] [12 Regression] wrong code with "-O3 -fno-tree-sra"
Date: Thu, 10 Jun 2021 09:28:09 +0000	[thread overview]
Message-ID: <bug-101009-4-QudfRkraUn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101009-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needs-bisection, wrong-code
   Target Milestone|---                         |12.0
            Summary|wrong code with "-O3        |[12 Regression] wrong code
                   |-fno-tree-sra"              |with "-O3 -fno-tree-sra"
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2021-06-10
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.  loop distribution distributes

  <bb 3> [local count: 955630225]:
  # d.2_15 = PHI <_2(6), d.2_14(5)>
  g[1].b = 2;
  g[1].c = 1;
  f.0_1 = f;
  *f.0_1 = g[1];
  g ={v} {CLOBBER};
  _2 = d.2_15 + -1;
  d = _2;
  if (_2 != 0)

to

  <bb 10> [local count: 955630225]:
  # d.2_17 = PHI <_22(11), d.2_14(5)>
  g[1].b = 2;
  f.0_19 = f;
  *f.0_19 = g[1];
  _22 = d.2_17 + -1;
  d = _22;
  if (_22 != 0)

and

  <bb 3> [local count: 955630225]:
  # d.2_15 = PHI <_2(6), d.2_14(8)>
  g[1].c = 1;
  _2 = d.2_15 + -1;
  if (_2 != 0)

doesn't seem to happen with the GCC 11 copy I have around.

  reply	other threads:[~2021-06-10  9:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10  8:17 [Bug tree-optimization/101009] New: " suochenyao at 163 dot com
2021-06-10  9:28 ` rguenth at gcc dot gnu.org [this message]
2021-06-10  9:40 ` [Bug tree-optimization/101009] [12 Regression] " rguenth at gcc dot gnu.org
2021-06-10 13:38 ` jakub at gcc dot gnu.org
2021-06-11  6:08 ` rguenth at gcc dot gnu.org
2021-06-11  6:23 ` rguenth at gcc dot gnu.org
2021-06-11  6:41 ` rguenth at gcc dot gnu.org
2021-06-11  7:19 ` rguenth at gcc dot gnu.org
2021-06-11  7:21 ` [Bug tree-optimization/101009] [10/11/12 " rguenth at gcc dot gnu.org
2021-06-11  7:33 ` rguenth at gcc dot gnu.org
2021-06-11  9:15 ` jakub at gcc dot gnu.org
2021-06-11  9:26 ` cvs-commit at gcc dot gnu.org
2021-06-11  9:27 ` [Bug tree-optimization/101009] [10/11 " rguenth at gcc dot gnu.org
2021-06-16 13:12 ` cvs-commit at gcc dot gnu.org
2021-09-06 10:18 ` [Bug tree-optimization/101009] [10 " cvs-commit at gcc dot gnu.org
2021-09-06 10:18 ` 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-101009-4-QudfRkraUn@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).