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/110009] Another missing ABS detection Date: Mon, 04 Sep 2023 09:00:24 +0000 [thread overview] Message-ID: <bug-110009-4-3dGoIDZQCc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110009-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110009 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Vector testcases too: ``` #define vector __attribute__((vector_size(4*sizeof(int)))) vector int signed_f1(vector int v) { vector int b_5; vector int _7; vector int _9; b_5 = v>>(sizeof(int)*8 - 1); _9 = b_5 | 1; _7 = v * _9; return _7; } vector unsigned unsigned_f1 (vector int v) { vector unsigned int d_6; vector int b_5; vector unsigned int v1_2; vector unsigned int _7; vector int _9; b_5 = v>>(sizeof(int)*8 - 1); _9 = b_5 | 1; d_6 = (vector unsigned int) _9; v1_2 = (vector unsigned int) v; _7 = v1_2 * d_6; return _7; } ``` Which does work with the match pattern in comment #5.
next prev parent reply other threads:[~2023-09-04 9:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-28 0:18 [Bug tree-optimization/110009] New: " pinskia at gcc dot gnu.org 2023-05-28 9:36 ` [Bug tree-optimization/110009] " gjl at gcc dot gnu.org 2023-05-28 14:38 ` pinskia at gcc dot gnu.org 2023-07-12 6:26 ` pinskia at gcc dot gnu.org 2023-09-04 8:20 ` pinskia at gcc dot gnu.org 2023-09-04 8:39 ` pinskia at gcc dot gnu.org 2023-09-04 9:00 ` pinskia at gcc dot gnu.org [this message] 2023-09-04 18:09 ` pinskia at gcc dot gnu.org 2023-09-04 18:10 ` pinskia 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-110009-4-3dGoIDZQCc@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).