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/115337] wrong code with _BitInt() __builtin_stdc_first_leading_one() at -O2 Date: Tue, 04 Jun 2024 04:28:01 +0000 [thread overview] Message-ID: <bug-115337-4-2KaaZFnbLk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115337-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115337 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |aldyh at gcc dot gnu.org, | |pinskia at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2024-06-04 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. # RANGE [irange] int [0, +INF] _1 = .CLZ (_2, -1); Is WRONG in evrp. The range is [-1, +INF]. Reduced testcase: ``` [[gnu::noinline]] int foo (unsigned _BitInt (129) z) { int t = __builtin_stdc_first_leading_one (z); return t == 0; } int main() { if (! foo(0)) __builtin_abort(); } ```
next prev parent reply other threads:[~2024-06-04 4:28 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-04 3:46 [Bug tree-optimization/115337] New: " zsojka at seznam dot cz 2024-06-04 4:28 ` pinskia at gcc dot gnu.org [this message] 2024-06-04 5:16 ` [Bug tree-optimization/115337] wrong code with _BitInt() __builtin_stdc_first_leading_one/__builtin_clzg (with -1 as second arg) " pinskia at gcc dot gnu.org 2024-06-04 8:58 ` jakub at gcc dot gnu.org 2024-06-04 10:12 ` jakub at gcc dot gnu.org 2024-06-04 10:13 ` jakub at gcc dot gnu.org 2024-06-04 10:14 ` jakub at gcc dot gnu.org 2024-06-04 10:15 ` jakub at gcc dot gnu.org 2024-06-04 13:52 ` cvs-commit at gcc dot gnu.org 2024-06-04 13:53 ` cvs-commit at gcc dot gnu.org 2024-06-04 14:17 ` cvs-commit at gcc dot gnu.org 2024-06-04 14:26 ` cvs-commit at gcc dot gnu.org 2024-06-04 14:30 ` jakub at gcc dot gnu.org 2024-06-04 14:30 ` jakub at gcc dot gnu.org 2024-06-11 6:17 ` cvs-commit at gcc dot gnu.org 2024-06-11 10:39 ` cvs-commit at gcc dot gnu.org 2024-06-20 13:24 ` 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-115337-4-2KaaZFnbLk@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).