public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109011] missed optimization in presence of __builtin_ctz Date: Mon, 06 Mar 2023 09:22:50 +0000 [thread overview] Message-ID: <bug-109011-4-Wd0FckNL1v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109011-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109011 --- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Testcase for the normal SI -> SI stuff might be something like with e.g. -O3 -mavx512{bw,cd,vl,dq,bitalg,vpopcntdq} -mbmi -mlzcnt options or so (the intent of the last 2 is to make clz/ctz defined at zero in GIMPLE). Plus similar testcase with long long * instead of int * and ll suffixed builtins. And also with unsigned char * and unsigned short * too eventually. void foo (int *p, int *q) { for (int i = 0; i < 2048; ++i) p[i] = __builtin_popcount (q[i]); } void bar (int *p, int *q) { for (int i = 0; i < 2048; ++i) p[i] = __builtin_clz (q[i]); } void baz (int *p, int *q) { for (int i = 0; i < 2048; ++i) p[i] = __builtin_ffs (q[i]); } void qux (int *p, int *q) { for (int i = 0; i < 2048; ++i) p[i] = __builtin_ctz (q[i]); } void corge (int *p, int *q) { for (int i = 0; i < 2048; ++i) p[i] = q[i] ? __builtin_clz (q[i]) : 32; } void grault (int *p, int *q) { for (int i = 0; i < 2048; ++i) p[i] = q[i] ? __builtin_ctz (q[i]) : 32; }
next prev parent reply other threads:[~2023-03-06 9:22 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-03 14:56 [Bug tree-optimization/109011] New: " vincenzo.innocente at cern dot ch 2023-03-03 19:45 ` [Bug tree-optimization/109011] " pinskia at gcc dot gnu.org 2023-03-03 19:48 ` pinskia at gcc dot gnu.org 2023-03-03 20:21 ` jakub at gcc dot gnu.org 2023-03-03 20:39 ` jakub at gcc dot gnu.org 2023-03-03 20:46 ` jakub at gcc dot gnu.org 2023-03-04 0:18 ` jakub at gcc dot gnu.org 2023-03-04 11:14 ` jakub at gcc dot gnu.org 2023-03-04 12:22 ` jakub at gcc dot gnu.org 2023-03-04 14:01 ` jakub at gcc dot gnu.org 2023-03-04 15:08 ` jakub at gcc dot gnu.org 2023-03-06 5:26 ` crazylht at gmail dot com 2023-03-06 7:01 ` jakub at gcc dot gnu.org 2023-03-06 7:59 ` crazylht at gmail dot com 2023-03-06 8:11 ` jakub at gcc dot gnu.org 2023-03-06 8:23 ` crazylht at gmail dot com 2023-03-06 8:32 ` jakub at gcc dot gnu.org 2023-03-06 9:22 ` jakub at gcc dot gnu.org [this message] 2023-03-14 9:24 ` crazylht at gmail dot com 2023-03-16 6:32 ` crazylht at gmail dot com 2023-04-19 9:15 ` cvs-commit at gcc dot gnu.org 2023-04-20 9:56 ` cvs-commit at gcc dot gnu.org 2023-04-20 17:45 ` cvs-commit at gcc dot gnu.org 2023-04-24 1:35 ` cvs-commit 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-109011-4-Wd0FckNL1v@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).