public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112468] [14 Regression] Missed phi-opt after recent change (phi-opt-24.c)
Date: Thu, 14 Dec 2023 00:36:53 +0000	[thread overview]
Message-ID: <bug-112468-4-FfhRsACh8c@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112468-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Tamar Christina from comment #10)
> Hi,
> 
> It's not forgotten. I've agreed on a fix with the maintainers that should
> solve a bunch of other (older) issues with copysign as well.
> 
> Since it's a bug fix it's on my list after my stage3 changes.  But I expect
> to be able to send the patch next week.
> 
> Sorry for the delay.

Fair enough, thanks for the update!

  parent reply	other threads:[~2023-12-14  0:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 19:55 [Bug tree-optimization/112468] New: [14 Regression] Missed phi-opt after recent change law at gcc dot gnu.org
2023-11-09 20:05 ` [Bug tree-optimization/112468] " pinskia at gcc dot gnu.org
2023-11-10  3:55 ` pinskia at gcc dot gnu.org
2023-11-10  4:06 ` pinskia at gcc dot gnu.org
2023-11-10  7:25 ` tnfchris at gcc dot gnu.org
2023-11-10  7:52 ` pinskia at gcc dot gnu.org
2023-11-10  8:31 ` rguenth at gcc dot gnu.org
2023-11-13  1:22 ` hp at gcc dot gnu.org
2023-11-13  7:04 ` tnfchris at gcc dot gnu.org
2023-12-10 19:34 ` pinskia at gcc dot gnu.org
2023-12-13 15:41 ` [Bug tree-optimization/112468] [14 Regression] Missed phi-opt after recent change (phi-opt-24.c) hp at gcc dot gnu.org
2023-12-13 15:44 ` tnfchris at gcc dot gnu.org
2023-12-14  0:36 ` hp at gcc dot gnu.org [this message]
2023-12-19  2:40 ` sandra at gcc dot gnu.org
2024-01-10 17:19 ` cvs-commit at gcc dot gnu.org
2024-01-10 17:21 ` tnfchris 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-112468-4-FfhRsACh8c@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).