public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101755] [12 regression] gcc.target/arm/reg_equal_test.c fails on arm since r12-2637 Date: Mon, 09 Aug 2021 21:02:17 +0000 [thread overview] Message-ID: <bug-101755-4-VLduCREowX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101755-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101755 --- Comment #1 from Andrew Macleod <amacleod at redhat dot com> --- What is that suppose to test? The range ecosystem has gotten smarter and we basically fold that function away to return 0 now. between EVRP, VRP and threading, you'd have to turn off a lot of optimizations to return to the original state.. I can't find a sequence.
next prev parent reply other threads:[~2021-08-09 21:02 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 15:27 [Bug tree-optimization/101755] New: " clyon at gcc dot gnu.org 2021-08-03 15:27 ` [Bug tree-optimization/101755] " clyon at gcc dot gnu.org 2021-08-09 21:02 ` amacleod at redhat dot com [this message] 2021-08-09 21:19 ` pinskia at gcc dot gnu.org 2022-03-08 14:09 ` rguenth at gcc dot gnu.org 2022-04-12 12:33 ` rearnsha at gcc dot gnu.org 2022-04-12 12:39 ` cvs-commit at gcc dot gnu.org 2022-04-12 12:41 ` rearnsha 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-101755-4-VLduCREowX@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).