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/105135] [11/12/13 Regression] Optimization regression for handrolled branchless assignment since r11-4717-g3e190757fa332d32 Date: Sat, 11 Mar 2023 05:32:28 +0000 [thread overview] Message-ID: <bug-105135-4-JGTnkfZoub@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105135-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105135 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|target |tree-optimization --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- For aarch64 to_lower_1/to_lower_2 is better: and w0, w0, 255 sub w1, w0, #65 and w1, w1, 255 cmp w1, 25 cset w1, ls add w0, w0, w1, lsl 5 ret vs and w0, w0, 255 sub w2, w0, #65 add w1, w0, 32 and w2, w2, 255 and w1, w1, 255 cmp w2, 25 csel w0, w0, w1, hi ret
next prev parent reply other threads:[~2023-03-11 5:32 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-02 8:53 [Bug middle-end/105135] New: [11/12 Regression] Optimization regression for handrolled branchless assignment andre.schackier at gmail dot com 2022-04-04 7:17 ` [Bug middle-end/105135] " rguenth at gcc dot gnu.org 2022-04-04 9:47 ` [Bug middle-end/105135] [11/12 Regression] Optimization regression for handrolled branchless assignment since r11-4717-g3e190757fa332d32 marxin at gcc dot gnu.org 2022-04-04 11:49 ` jakub at gcc dot gnu.org 2022-04-21 7:51 ` rguenth at gcc dot gnu.org 2022-07-26 12:37 ` [Bug target/105135] [11/12/13 " rguenth at gcc dot gnu.org 2022-07-26 13:36 ` amonakov at gcc dot gnu.org 2023-03-11 5:29 ` pinskia at gcc dot gnu.org 2023-03-11 5:32 ` pinskia at gcc dot gnu.org [this message] 2023-05-29 10:06 ` [Bug tree-optimization/105135] [11/12/13/14 " 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-105135-4-JGTnkfZoub@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).