public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111727] [14 Regression] wrong code at -O3 on x86_64-linux-gnu
Date: Sun, 08 Oct 2023 16:50:11 +0000	[thread overview]
Message-ID: <bug-111727-4-VGom0gOgn5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111727-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
            Version|unknown                     |14.0
           Keywords|                            |wrong-code
   Target Milestone|---                         |14.0
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-10-08
            Summary|wrong code at -O3 on        |[14 Regression] wrong code
                   |x86_64-linux-gnu            |at -O3 on x86_64-linux-gnu

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.

  reply	other threads:[~2023-10-08 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-08 16:34 [Bug tree-optimization/111727] New: " zhendong.su at inf dot ethz.ch
2023-10-08 16:50 ` pinskia at gcc dot gnu.org [this message]
2023-10-13  6:31 ` [Bug tree-optimization/111727] [14 Regression] " zhendong.su at inf dot ethz.ch
2023-10-17 13:06 ` rguenth at gcc dot gnu.org
2023-10-17 13:54 ` ppalka at gcc dot gnu.org
2023-11-14 14:13 ` [Bug tree-optimization/111727] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-2944-g3d48c11ad082de cvs-commit at gcc dot gnu.org
2023-11-14 14:15 ` 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-111727-4-VGom0gOgn5@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).