public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/97386] [8/9 Regression] wrong code with __builtin_bswap16() of rotated 64bit value Date: Thu, 22 Apr 2021 16:48:41 +0000 [thread overview] Message-ID: <bug-97386-4-1HOM4LeBdl@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 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-8 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:615b19069a9afd9faf803d6888ac49d03065762d commit r8-10860-g615b19069a9afd9faf803d6888ac49d03065762d Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Oct 13 19:13:26 2020 +0200 combine: Fix up simplify_shift_const_1 for nested ROTATEs [PR97386] The following testcases are miscompiled (the first one since my improvements to rotate discovery on GIMPLE, the other one for many years) because combiner optimizes nested ROTATEs with narrowing SUBREG in between (i.e. the outer rotate is performed in shorter precision than the inner one) to just one ROTATE of the rotated constant. While that (under certain conditions) can work for shifts, it can't work for rotates where we can only do that with rotates of the same precision. 2020-10-13 Jakub Jelinek <jakub@redhat.com> PR rtl-optimization/97386 * combine.c (simplify_shift_const_1): Don't optimize nested ROTATEs if they have different modes. * gcc.c-torture/execute/pr97386-1.c: New test. * gcc.c-torture/execute/pr97386-2.c: New test. (cherry picked from commit 1a98b22b0468214ae8463d075dacaeea1d46df15)
next prev parent reply other threads:[~2021-04-22 16:48 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-12 14:38 [Bug tree-optimization/97386] New: [8/9/10/11 " zsojka at seznam dot cz 2020-10-12 18:04 ` [Bug tree-optimization/97386] " jakub at gcc dot gnu.org 2020-10-12 19:52 ` 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 [this message] 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-1HOM4LeBdl@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).