public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108862] [13 Regression] CryptX miscompilation on power9 since r13-2107 Date: Mon, 20 Feb 2023 14:51:16 +0000 [thread overview] Message-ID: <bug-108862-4-ijtyUZNDcK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108862-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862 --- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> --- With -fno-unroll-loops added we get foo: .LFB0: .cfi_startproc cmpwi 0,3,0 ble 0,.L4 mtctr 3 addi 10,4,-8 addi 5,5,8 li 3,0 .p2align 4,,15 .L3: ldu 4,8(10) ldu 9,-8(5) maddld 3,4,9,3 maddhdu 4,4,9,3 bdnz .L3 blr .p2align 4,,15 .L4: li 3,0 li 4,0 blr (which still fails, just is easier to read). The destinations of the four inner loop insns were 131, 132, 135, 136, and IRA decided for those Disposition: 18:r131 l0 4 17:r132 l0 9 1:r135 l0 3 0:r136 l0 4 and that cannot fly.
next prev parent reply other threads:[~2023-02-20 14:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-20 14:20 [Bug target/108862] New: " jakub at gcc dot gnu.org 2023-02-20 14:20 ` [Bug target/108862] " jakub at gcc dot gnu.org 2023-02-20 14:27 ` jakub at gcc dot gnu.org 2023-02-20 14:36 ` jakub at gcc dot gnu.org 2023-02-20 14:51 ` segher at gcc dot gnu.org [this message] 2023-02-20 14:56 ` jakub at gcc dot gnu.org 2023-02-20 15:07 ` jakub at gcc dot gnu.org 2023-02-20 21:08 ` cvs-commit at gcc dot gnu.org 2023-02-20 21:12 ` 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-108862-4-ijtyUZNDcK@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).