public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/99230] New: [11 Regression] gcc.dg/pr83527.c excess errors: '-fcompare-debug' failure (length)
Date: Tue, 23 Feb 2021 21:40:31 +0000 [thread overview]
Message-ID: <bug-99230-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99230
Bug ID: 99230
Summary: [11 Regression] gcc.dg/pr83527.c excess errors:
'-fcompare-debug' failure (length)
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: hp at gcc dot gnu.org
CC: aoliva at gcc dot gnu.org, sandra at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-linux
Target: cris-elf
This test started to fail for cris-elf almost identically to the description in
PR83527 since 3696a50beeb73f4 / r11-3302 "Change C front end to emit structured
loop and switch tree nodes", but I don't see this failure for other targets in
the gcc-testresults@ archives (at least no search engine hits) and I can't find
an obvious target description oddity related to switches or case-tables.
Build machine is x86_64 stock Debian 9. A brief look at the commit fixing
PR83527 (18408e962e5a) didn't help with applying that to the mentioned switch
rewrite.
No extra tools are needed to repeat the problem, just configure with e.g.
"--target=cris-elf --enable-languages=c" and
"make all-gcc" then "make check-gcc-c RUNTESTFLAGS=dg.exp=pr83527.c"
(I use --target_board=cris-sim usually but that can be elided for this test.)
Perhaps of interest:
--- pr83527.gk.c.gkd 2021-02-23 16:02:07.985669417 +0100
+++ pr83527.c.gkd 2021-02-23 16:02:07.973669826 +0100
@@ -7,7 +7,7 @@ Declarations used by fn1, sorted by DECL
5: void <L0>;
2: void <L1>;
3: void <L2>;
-1: void <L9>;
+1: void <L10>;
;; Function fn1 (fn1, funcdef_no=0, cgraph_uid=1, symbol_order=2)
Testsuite run:
Running /x/gcc/gcc/testsuite/gcc.dg/dg.exp ...
... (lines elided)
FAIL: gcc.dg/pr83527.c (test for excess errors)
>From gcc.log:
xgcc: error: /x/gcc/gcc/testsuite/gcc.dg/pr83527.c: '-fcompare-debug' failure
(length)
next reply other threads:[~2021-02-23 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 21:40 hp at gcc dot gnu.org [this message]
2021-02-23 21:42 ` [Bug debug/99230] " hp at gcc dot gnu.org
2021-02-24 8:30 ` rguenth at gcc dot gnu.org
2021-02-24 16:59 ` jakub at gcc dot gnu.org
2021-02-26 12:59 ` rguenth at gcc dot gnu.org
2021-03-01 11:53 ` jakub at gcc dot gnu.org
2021-03-01 12:46 ` jakub at gcc dot gnu.org
2021-03-17 18:56 ` jakub at gcc dot gnu.org
2021-03-18 14:57 ` hp at gcc dot gnu.org
2021-03-20 16:02 ` cvs-commit at gcc dot gnu.org
2021-03-24 15:09 ` jakub 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-99230-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: link
Be 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).