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 target/108862] New: [13 Regression] CryptX miscompilation on power9 since r13-2107 Date: Mon, 20 Feb 2023 14:20:25 +0000 [thread overview] Message-ID: <bug-108862-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108862 Bug ID: 108862 Summary: [13 Regression] CryptX miscompilation on power9 since r13-2107 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org Target Milestone: --- The following testcase is miscompiled with -O2 -mcpu=power9 since r13-2107 and is not fixed with r13-5999 fix: unsigned long long a[2] = { 0x04a13945d898c296ULL, 0x0000100000000fffULL }; unsigned long long b[4] = { 0x04a13945d898c296ULL, 0, 0, 0x0000100000000fffULL }; __attribute__((noipa)) unsigned __int128 foo (int x, unsigned long long *y, unsigned long long *z) { unsigned __int128 w = 0; for (int i = 0; i < x; i++) w += (unsigned __int128)*y++ * (unsigned __int128)*z--; return w; } int main () { unsigned __int128 x = foo (1, &a[0], &a[1]); unsigned __int128 y = foo (2, &b[0], &b[3]); if ((unsigned long long) (x >> 64) != 0x0000004a13945dd3ULL || (unsigned long long) x != 0x9b1c8443b3909d6aULL || x != y) __builtin_abort (); return 0; }
next reply other threads:[~2023-02-20 14:20 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-20 14:20 jakub at gcc dot gnu.org [this message] 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 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@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).