public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102448] New: [12 Regression] wrong codegen in gcc in spec2017 since 24f99147b9264f8f7d9cfb2fa6bd431edfa252d2 Date: Wed, 22 Sep 2021 12:07:29 +0000 [thread overview] Message-ID: <bug-102448-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102448 Bug ID: 102448 Summary: [12 Regression] wrong codegen in gcc in spec2017 since 24f99147b9264f8f7d9cfb2fa6bd431edfa252d2 Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: tnfchris at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Target Milestone: --- Since g:24f99147b9264f8f7d9cfb2fa6bd431edfa252d2 we've been getting a segfault on gcc in spec2017. It looks like ira_init has been miscompiled and an additional unconditional store materialized: Before: add x1, x19, #0x4 add x2, x19, #0x14 ldr q0, [x0,#4064] str q0, [x1],#16 After: add x19, x19, #0x4 ldr q0, [x0,#4000] str q0, [x19],#16 str q0, [x19],#16 so it's pushing 16 bytes more into x19 than it did before. Trying to see if I can reduce a testcase
next reply other threads:[~2021-09-22 12:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-22 12:07 tnfchris at gcc dot gnu.org [this message] 2021-09-22 12:30 ` [Bug tree-optimization/102448] " rguenth at gcc dot gnu.org 2021-09-22 18:50 ` tnfchris at gcc dot gnu.org 2021-09-23 6:35 ` rguenth at gcc dot gnu.org 2021-09-23 6:54 ` rguenth at gcc dot gnu.org 2021-09-23 8:11 ` rguenth at gcc dot gnu.org 2021-09-23 9:17 ` cvs-commit at gcc dot gnu.org 2021-09-23 9:18 ` rguenth at gcc dot gnu.org 2021-09-23 9:21 ` tnfchris 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-102448-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).