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/110503] [13/14 Regression] Dead Code Elimination Regression at -O3 since r13-322-g7f04b0d786e
Date: Fri, 30 Jun 2023 22:29:47 +0000 [thread overview]
Message-ID: <bug-110503-4-5M8KNBvDBN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110503-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110503
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
>
> Oh and had:
> # RANGE [irange] int [-128, 127]
> _10 = (intD.6) _9;
> # RANGE [irange] int [0, 1] NONZERO 0x1
> _11 = 1 % _10;
>
> I wonder if we could optimize `1 % b` into just `b != 1` (since 1 % 0 is
> undefined) which will further reduce things here.
That does not change the size of the loop though and we are still left with:
size: 1 _10 = _9 == 1;
size: 0 _11 = (unsigned int) _10;
size: 1 _12 = -_11;
size: 2 if (_12 > 2)
But at least now we just need to optimize the above to just `if (_9 == 1)`
Something like:
(simplify
(gt (negative zero_one_value@0) INTEGER_CST@1)
(if (wi::to_wide (@1) >= 1 && TYPE_UNSIGNED (TREE_TYPE (@1)))
(ne @0 { build_zero_cst (TREE_TYPE (@1)); } )
(if (wi::to_wide (@1) >= 0 && !TYPE_UNSIGNED (TREE_TYPE (@1)))
(eq @0 { build_zero_cst (TREE_TYPE (@1)); } )
)
)
)
But I get the feeling this should be done in VRP instead of match ...
next prev parent reply other threads:[~2023-06-30 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 16:34 [Bug tree-optimization/110503] New: " theodort at inf dot ethz.ch
2023-06-30 21:21 ` [Bug tree-optimization/110503] " pinskia at gcc dot gnu.org
2023-06-30 21:42 ` pinskia at gcc dot gnu.org
2023-06-30 21:47 ` pinskia at gcc dot gnu.org
2023-06-30 22:29 ` pinskia at gcc dot gnu.org [this message]
2023-07-27 9:27 ` rguenth at gcc dot gnu.org
2023-08-07 9:08 ` pinskia at gcc dot gnu.org
2023-08-26 0:13 ` pinskia at gcc dot gnu.org
2024-03-08 15:28 ` law at gcc dot gnu.org
2024-03-09 7:16 ` law at gcc dot gnu.org
2024-05-21 9:16 ` [Bug tree-optimization/110503] [13/14/15 " jakub 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-110503-4-5M8KNBvDBN@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).