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/85390] [10/11/12/13/14 Regression] possible missed optimisation / regression from 6.3 with conditional expression
Date: Tue, 30 May 2023 07:41:51 +0000	[thread overview]
Message-ID: <bug-85390-4-9L5To0qqsC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-85390-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |14.0
   Target Milestone|10.5                        |14.0
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Fixed fully for GCC 14 by r14-573-g69f1a8af45d8a4 which pulls out the cast from
the branches and allows ifcvt to happen.

      parent reply	other threads:[~2023-05-30  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-85390-4@http.gcc.gnu.org/bugzilla/>
2021-07-20  0:55 ` [Bug rtl-optimization/85390] " pinskia at gcc dot gnu.org
2021-12-16  7:01 ` [Bug tree-optimization/85390] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-21 13:50 ` rguenth at gcc dot gnu.org
2022-01-31 14:45 ` marxin at gcc dot gnu.org
2022-05-27  9:38 ` [Bug tree-optimization/85390] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:35 ` jakub at gcc dot gnu.org
2023-05-30  7:41 ` pinskia at gcc dot gnu.org [this message]

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-85390-4-9L5To0qqsC@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).