public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103417] [12 Regression] wrong code at -O1 and above on x86_64-linux-gnu since r12-5489 Date: Thu, 25 Nov 2021 02:44:59 +0000 [thread overview] Message-ID: <bug-103417-4-zaMJRKuVjD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103417-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103417 --- Comment #5 from Tamar Christina <tnfchris at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #4) > Created attachment 51870 [details] > gcc12-pr103417.patch > > Untested fix. Handling GE in that simplification is clearly bogus, we > should just fold it to true elsewhere, not bother with it (it doesn't handle > LT either, > which should also fold to false elsewhere). Indeed, that one is wrong.. > Handling LE and GT there isn't wrong, but makes no sense. Elsewhere we > canonicalize x > 0U into x != 0U and x <= 0U into x == 0U and for signed it > was handling only EQ and NE already before. Well, the intention is to simplify the bitmask. Most vector ISAs can create the simple bitmask much easier than the complex one. i.e. 0xFFFFFF00 is much harder to create than 0xFF. for scalar yes it doesn't matter much. but e.g. for (int i = 0; i < (n & -16); i++) x[i] = (x[i]&(~255)) <= 0U; generates worse code when the mask 0xFFFFFF00 is to be used. The patch is mainly addressing vector code but we added scalar for uniformity. So I would like LE and GT to stay, at the very least for vector where it makes a difference. It's not something we can fix in the backend because we can't differentiate between signed and unsigned.
next prev parent reply other threads:[~2021-11-25 2:44 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-24 20:49 [Bug tree-optimization/103417] New: wrong code at -O1 and above on x86_64-linux-gnu zhendong.su at inf dot ethz.ch 2021-11-24 21:02 ` [Bug tree-optimization/103417] " pinskia at gcc dot gnu.org 2021-11-24 21:02 ` [Bug tree-optimization/103417] [12 Regression] " pinskia at gcc dot gnu.org 2021-11-24 21:03 ` [Bug tree-optimization/103417] [12 Regression] wrong code at -O1 and above on x86_64-linux-gnu since r12-5489 jakub at gcc dot gnu.org 2021-11-24 21:16 ` jakub at gcc dot gnu.org 2021-11-24 21:45 ` jakub at gcc dot gnu.org 2021-11-25 2:44 ` tnfchris at gcc dot gnu.org [this message] 2021-11-25 9:48 ` cvs-commit at gcc dot gnu.org 2021-11-25 15:22 ` 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-103417-4-zaMJRKuVjD@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: linkBe 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).