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/111472] [11/12/13/14 Regression] Wrong code at -Os on x86_64-linux-gnu since r11-4563-gd0d8b5d836
Date: Mon, 06 Nov 2023 20:37:24 +0000	[thread overview]
Message-ID: <bug-111472-4-Jijkr3X2Wg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111472-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Macleod from comment #3)
> I'm not sure that this didn't uncover something elsewhere, possibly ivopts
> since that pass seems to be generating something different and I think there
> were some fixes put in there on trunk?.
> 
> Regardless, this currently works on trunk. Can we run a regression on trunk
> and see what patch fixed it? 

Most likely  r14-4789-g44e7e4498c (aka PR 110243).

  parent reply	other threads:[~2023-11-06 20:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  7:38 [Bug c/111472] New: Wrong code at -Os on x86_64-linux-gnu since shaohua.li at inf dot ethz.ch
2023-09-19  7:45 ` [Bug tree-optimization/111472] Wrong code at -Os on x86_64-linux-gnu since r11-4563-gd0d8b5d836 xry111 at gcc dot gnu.org
2023-09-19  7:47 ` shaohua.li at inf dot ethz.ch
2023-09-19  7:48 ` [Bug tree-optimization/111472] [11/12/13/14 Regression] " xry111 at gcc dot gnu.org
2023-09-19  7:48 ` pinskia at gcc dot gnu.org
2023-11-06 20:31 ` amacleod at redhat dot com
2023-11-06 20:35 ` amacleod at redhat dot com
2023-11-06 20:37 ` pinskia at gcc dot gnu.org [this message]
2024-03-07 22:24 ` [Bug tree-optimization/111472] [11/12/13 " law at gcc dot gnu.org
2024-05-08 12:15 ` [Bug tree-optimization/111472] [11 " 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-111472-4-Jijkr3X2Wg@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).