public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115478] [15 Regression] gcc.target/aarch64/bitint-args.c fails Date: Thu, 13 Jun 2024 16:11:10 +0000 [thread overview] Message-ID: <bug-115478-4-oEhM05p8OH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115478-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115478 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |law at gcc dot gnu.org Status|UNCONFIRMED |NEW Last reconfirmed| |2024-06-13 --- Comment #2 from Jeffrey A. Law <law at gcc dot gnu.org> --- Those look worse than the original, so I don't think we want to blindly change the expected output. We need to understand the delta a bit better. My suspicion is we had a combiner pattern in the aarch64 backend that triggered on the old (unsimplified) form which doesn't after the RTL simplifications. It's on my list, but I haven't gotten to it yet.
next prev parent reply other threads:[~2024-06-13 16:11 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-13 15:36 [Bug c/115478] New: " carlos.seo at linaro dot org 2024-06-13 15:42 ` [Bug c/115478] " pinskia at gcc dot gnu.org 2024-06-13 15:43 ` [Bug target/115478] " pinskia at gcc dot gnu.org 2024-06-13 16:11 ` law at gcc dot gnu.org [this message] 2024-06-13 20:49 ` roger at nextmovesoftware dot com 2024-06-14 14:32 ` law at gcc dot gnu.org 2024-06-24 20:51 ` [Bug target/115478] [15 Regression] gcc.target/aarch64/bitint-args.c fails since r15-1120-g2277f987979445 rsandifo 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-115478-4-oEhM05p8OH@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).