public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101541] Missing ABSU detection at gimple
Date: Tue, 24 Oct 2023 11:17:45 +0000 [thread overview]
Message-ID: <bug-101541-4-jbt6RjIPJG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101541-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101541
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:
https://gcc.gnu.org/g:0fc13e8c0e39c51e82deb93f324d9d86ad8d7460
commit r14-4889-g0fc13e8c0e39c51e82deb93f324d9d86ad8d7460
Author: Andrew Pinski <pinskia@gmail.com>
Date: Sun Oct 15 19:15:38 2023 +0000
Improve factor_out_conditional_operation for conversions and constants
In the case of a NOP conversion (precisions of the 2 types are equal),
factoring out the conversion can be done even if int_fits_type_p returns
false and even when the conversion is defined by a statement inside the
conditional. Since it is a NOP conversion there is no zero/sign extending
happening which is why it is ok to be done here; we were trying to prevent
an extra sign/zero extend from being moved away from definition which no-op
conversions are not.
Bootstrapped and tested on x86_64-linux-gnu with no regressions.
gcc/ChangeLog:
PR tree-optimization/104376
PR tree-optimization/101541
* tree-ssa-phiopt.cc (factor_out_conditional_operation):
Allow nop conversions even if it is defined by a statement
inside the conditional.
gcc/testsuite/ChangeLog:
PR tree-optimization/101541
* gcc.dg/tree-ssa/phi-opt-39.c: New test.
prev parent reply other threads:[~2023-10-24 11:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 22:58 [Bug tree-optimization/101541] New: " pinskia at gcc dot gnu.org
2021-07-21 7:01 ` [Bug tree-optimization/101541] " rguenth at gcc dot gnu.org
2021-11-20 10:58 ` pinskia at gcc dot gnu.org
2021-11-20 22:03 ` pinskia at gcc dot gnu.org
2023-05-04 0:01 ` pinskia at gcc dot gnu.org
2023-10-15 16:59 ` pinskia at gcc dot gnu.org
2023-10-15 17:42 ` pinskia at gcc dot gnu.org
2023-10-15 19:24 ` pinskia at gcc dot gnu.org
2023-10-15 22:00 ` pinskia at gcc dot gnu.org
2023-10-16 17:11 ` cvs-commit at gcc dot gnu.org
2023-10-16 17:15 ` pinskia at gcc dot gnu.org
2023-10-24 11:17 ` cvs-commit 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-101541-4-jbt6RjIPJG@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).