public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/103873] [12 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Fri, 31 Dec 2021 15:26:11 +0000	[thread overview]
Message-ID: <bug-103873-4-aiddI8WWkx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103873-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |matz at gcc dot gnu.org
            Summary|wrong code at -O3 on        |[12 Regression] wrong code
                   |x86_64-linux-gnu            |at -O3 on x86_64-linux-gnu
             Status|UNCONFIRMED                 |NEW
            Version|unknown                     |12.0
           Priority|P3                          |P1
   Target Milestone|---                         |12.0
   Last reconfirmed|                            |2021-12-31

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started to ICE with r12-4526-gd8edfadfc7a9795b65177a50ce44fd348858e844
(before it compiled and executed fine) and starting with
r12-5264-gd1ca8aeaf34a717dffd8f4a1f0333d25c7d1c904 it doesn't ICE anymore but
is instead miscompiled.
Perhaps related to PR103300 ?

  reply	other threads:[~2021-12-31 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 10:55 [Bug tree-optimization/103873] New: " zhendong.su at inf dot ethz.ch
2021-12-31 15:26 ` jakub at gcc dot gnu.org [this message]
2022-02-15 12:54 ` [Bug tree-optimization/103873] [12 Regression] " 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-103873-4-aiddI8WWkx@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).