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/97386] [8/9/10/11 Regression] wrong code with __builtin_bswap16() of rotated 64bit value Date: Mon, 12 Oct 2020 18:04:53 +0000 [thread overview] Message-ID: <bug-97386-4-tIqK24RDfh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97386-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97386 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |8.5 Status|UNCONFIRMED |ASSIGNED CC| |jakub at gcc dot gnu.org Last reconfirmed| |2020-10-12 Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with my r8-3824-ga0e4174cd80f8a17026d6c13af2802dc8a0146ad unsigned int c; unsigned char foo (void) { return __builtin_bswap16 ((unsigned long long) (0xccccLLU << c | 0xccccLLU >> ((-c) & 63))); } int main (void) { unsigned char x = foo (); if (__CHAR_BIT__ == 8 && x != 0xcc) __builtin_abort (); return 0; }
next prev parent reply other threads:[~2020-10-12 18:04 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 14:38 [Bug tree-optimization/97386] New: " zsojka at seznam dot cz 2020-10-12 18:04 ` jakub at gcc dot gnu.org [this message] 2020-10-12 19:52 ` [Bug tree-optimization/97386] " jakub at gcc dot gnu.org 2020-10-12 19:56 ` jakub at gcc dot gnu.org 2020-10-13 17:14 ` cvs-commit at gcc dot gnu.org 2020-10-16 11:37 ` cvs-commit at gcc dot gnu.org 2020-10-16 11:38 ` [Bug tree-optimization/97386] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:29 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:48 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:07 ` 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-97386-4-tIqK24RDfh@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).