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 debug/100523] New: [11/12 Regression] armv8.1-m.main -fcompare-debug failure with -O -fmodulo-sched -mtune=cortex-a53 Date: Tue, 11 May 2021 14:39:25 +0000 [thread overview] Message-ID: <bug-100523-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100523 Bug ID: 100523 Summary: [11/12 Regression] armv8.1-m.main -fcompare-debug failure with -O -fmodulo-sched -mtune=cortex-a53 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: acoplan at gcc dot gnu.org Target Milestone: --- The following fails: $ cat test.c int main_j; int main() { long crc; for (; main_j; main_j--) if (crc) crc = crc >> 1 ^ 20; } $ ./arm-eabi-gcc -c test.c -fcompare-debug -O -fmodulo-sched -march=armv8.1-m.main -mfloat-abi=soft -mtune=cortex-a53 arm-eabi-gcc: error: test.c: '-fcompare-debug' failure Obviously the choice of scheduling isn't sensible for this -march, but it reveals a bug in any case.
next reply other threads:[~2021-05-11 14:39 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 14:39 acoplan at gcc dot gnu.org [this message] 2021-05-12 6:39 ` [Bug debug/100523] " rguenth at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2022-11-04 20:53 ` [Bug debug/100523] [11/12/13 " ramana at gcc dot gnu.org 2022-11-07 10:33 ` acoplan at gcc dot gnu.org 2023-05-29 10:04 ` [Bug debug/100523] [11/12/13/14 " jakub at gcc dot gnu.org 2024-03-04 1:58 ` law at gcc dot gnu.org 2024-03-06 10:25 ` 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-100523-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).