public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/108140] ICE expanding __rbit Date: Fri, 16 Dec 2022 09:35:29 +0000 [thread overview] Message-ID: <bug-108140-4-8R0TBojHuf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108140-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108140 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org Keywords| |ice-on-valid-code Component|c |middle-end Target| |aarch64-*-* Summary|tzcnt gives different |ICE expanding __rbit |result in debug vs release | --- Comment #4 from Alexander Monakov <amonakov at gcc dot gnu.org> --- When comment #0 says "this crashes at -O2", it means ICE in expand for the '__rbit' intrinsic on this testcase, which is reproducible on 12.2 and trunk: #include<stdio.h> #include<arm_acle.h> int main(int argc, char *argv[]) { unsigned long long input = argc-1; unsigned long long v = __clz(__rbit(input)); printf("%d %d\n", argc, v >= 64 ? 123 : 456); } I've edited the bug title to reflect this.
next prev parent reply other threads:[~2022-12-16 9:35 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-16 8:18 [Bug c/108140] New: tzcnt gives different result in debug vs release levo.delellis at gmail dot com 2022-12-16 8:28 ` [Bug c/108140] " jakub at gcc dot gnu.org 2022-12-16 8:29 ` jakub at gcc dot gnu.org 2022-12-16 8:45 ` levo.delellis at gmail dot com 2022-12-16 9:35 ` amonakov at gcc dot gnu.org [this message] 2022-12-16 11:55 ` [Bug middle-end/108140] ICE expanding __rbit ktkachov at gcc dot gnu.org 2022-12-19 11:19 ` [Bug target/108140] " cvs-commit at gcc dot gnu.org 2023-01-10 10:26 ` cvs-commit at gcc dot gnu.org 2023-05-08 12:26 ` rguenth at gcc dot gnu.org 2023-05-09 9:04 ` ktkachov 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-108140-4-8R0TBojHuf@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).