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 middle-end/110015] openjpeg is slower when built with gcc13 compared to clang16
Date: Tue, 07 Nov 2023 02:42:04 +0000 [thread overview]
Message-ID: <bug-110015-4-EPD8Vl0vYS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110015-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110015
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |112418
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> After fixing PR 112324 (and a secondary patch to phiopt to do
> factor_out_conditional_operation for all phi nodes rather than just a single
> one) we still miss the abs detection:
Filed PR 112418 for the secondary patch.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112418
[Bug 112418] factor_out_conditional_operation could be done for more phis
next prev parent reply other threads:[~2023-11-07 2:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 19:15 [Bug middle-end/110015] New: " hubicka at gcc dot gnu.org
2023-05-28 19:42 ` [Bug middle-end/110015] " hubicka at gcc dot gnu.org
2023-10-31 12:08 ` zhangjungcc at gmail dot com
2023-11-01 1:15 ` crazylht at gmail dot com
2023-11-01 1:28 ` crazylht at gmail dot com
2023-11-07 1:12 ` pinskia at gcc dot gnu.org
2023-11-07 2:14 ` pinskia at gcc dot gnu.org
2023-11-07 2:14 ` pinskia at gcc dot gnu.org
2023-11-07 2:42 ` pinskia at gcc dot gnu.org [this message]
2023-11-07 2:50 ` pinskia at gcc dot gnu.org
2023-11-24 23:22 ` hubicka 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-110015-4-EPD8Vl0vYS@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).