public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112922] [14 Regression] 465.tonto from SPECFP 2006 fails train run on Aarch64-linux with -O2 and -flto Date: Tue, 20 Feb 2024 11:56:18 +0000 [thread overview] Message-ID: <bug-112922-4-cf2xxBxfKy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112922-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112922 Alex Coplan <acoplan at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |acoplan at gcc dot gnu.org, | |rsandifo at gcc dot gnu.org --- Comment #1 from Alex Coplan <acoplan at gcc dot gnu.org> --- So I did some bisection on this, and indeed it seems to have started with r14-6290-g9f0f7d802482a8958d6cdc72f1fe0c8549db2182 i.e. commit 9f0f7d802482a8958d6cdc72f1fe0c8549db2182 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Thu Dec 7 19:41:19 2023 aarch64: Add an early RA for strided registers but then it seemed to get fixed shortly afterwards by r14-6339-g8b5cd6c4519cc120badd2b35a9e30d4deb82c012 i.e. commit 8b5cd6c4519cc120badd2b35a9e30d4deb82c012 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Fri Dec 8 16:27:40 2023 aarch64: Some tweaks to the early-ra pass CCing Richard S who can hopefully confirm if that change was expected to fix correctness / wrong code issues.
next prev parent reply other threads:[~2024-02-20 11:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-08 14:56 [Bug target/112922] New: " jamborm at gcc dot gnu.org 2023-12-08 19:28 ` [Bug target/112922] [14 Regression] " pinskia at gcc dot gnu.org 2024-02-20 11:56 ` acoplan at gcc dot gnu.org [this message] 2024-02-20 19:05 ` rsandifo at gcc dot gnu.org 2024-02-23 14:17 ` 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-112922-4-cf2xxBxfKy@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).