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 rtl-optimization/98334] Failure to optimally optimize add loop to mul
Date: Fri, 17 Feb 2023 18:35:31 +0000 [thread overview]
Message-ID: <bug-98334-4-CQmFhN1jrn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98334-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98334
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |13.0
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> Fixed at the RTL level, keeping open for the GIMPLE optimization.
For the testcase in comment #1 this is recorded as PR 94782.
For the original testcase in comment #0, I don't know when it was fixed on the
trunk but in sccp we get now:
final value replacement:
result_2 = PHI <result_7(3)>
with expr: (int) n_4(D) * i_6(D)
final stmt:
result_2 = _1 * i_6(D);
instead of:
final value replacement:
result_2 = PHI <result_7(3)>
with expr: (int) (n_3(D) + 4294967295) * i_6(D) + i_6(D)
final stmt:
result_2 = _9 + i_6(D);
prev parent reply other threads:[~2023-02-17 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 18:48 [Bug tree-optimization/98334] New: " gabravier at gmail dot com
2020-12-17 10:04 ` [Bug tree-optimization/98334] " jakub at gcc dot gnu.org
2020-12-17 10:59 ` [Bug rtl-optimization/98334] " jakub at gcc dot gnu.org
2021-01-04 15:36 ` rguenth at gcc dot gnu.org
2021-01-05 9:59 ` cvs-commit at gcc dot gnu.org
2021-01-05 10:01 ` jakub at gcc dot gnu.org
2022-05-27 20:34 ` roger at nextmovesoftware dot com
2023-02-17 18:35 ` 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-98334-4-CQmFhN1jrn@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).