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/100520] New: [11/12 Regression] aarch64: ‘-fcompare-debug’ failure with -fprofile-generate Date: Tue, 11 May 2021 13:52:46 +0000 [thread overview] Message-ID: <bug-100520-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100520 Bug ID: 100520 Summary: [11/12 Regression] aarch64: ‘-fcompare-debug’ failure with -fprofile-generate 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: --- With GCC 11 and trunk I'm seeing the following -fcompare-debug problem: $ cat test.c static int f() {} $ aarch64-linux-gnu-gcc -c test.c -fcompare-debug -fprofile-generate aarch64-linux-gnu-gcc: error: test.c: ‘-fcompare-debug’ failure
next reply other threads:[~2021-05-11 13:52 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-11 13:52 acoplan at gcc dot gnu.org [this message] 2021-05-12 6:36 ` [Bug debug/100520] " rguenth at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2021-09-20 7:00 ` [Bug debug/100520] [11/12 Regression] " pinskia at gcc dot gnu.org 2021-09-20 7:05 ` pinskia at gcc dot gnu.org 2021-09-20 7:12 ` [Bug gcov-profile/100520] " pinskia at gcc dot gnu.org 2021-09-27 11:54 ` marxin at gcc dot gnu.org 2021-11-05 15:01 ` [Bug gcov-profile/100520] [11/12 Regression] ‘-fcompare-debug’ failure with -fprofile-generate since r11-627-g1dedc12d186a1108 marxin at gcc dot gnu.org 2021-11-05 15:15 ` marxin at gcc dot gnu.org 2021-11-08 11:52 ` cvs-commit at gcc dot gnu.org 2021-11-08 11:54 ` [Bug gcov-profile/100520] [11 " marxin at gcc dot gnu.org 2021-11-08 12:26 ` cvs-commit at gcc dot gnu.org 2021-11-08 12:27 ` marxin 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-100520-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).