public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug debug/94296] New: [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375
@ 2020-03-24 9:11 marxin at gcc dot gnu.org
2020-03-24 9:11 ` [Bug debug/94296] " marxin at gcc dot gnu.org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: marxin at gcc dot gnu.org @ 2020-03-24 9:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94296
Bug ID: 94296
Summary: [10 Regression] gcc: error:
gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’
failure (length) since r10-4482-gaea86742ce396375
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
I see the following error:
$ gcc gcc/testsuite/gcc.dg/cleanup-13.c -fno-asynchronous-unwind-tables
-fcompare-debug
gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure
(length)
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug debug/94296] [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375
2020-03-24 9:11 [Bug debug/94296] New: [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375 marxin at gcc dot gnu.org
@ 2020-03-24 9:11 ` marxin at gcc dot gnu.org
2020-03-24 10:55 ` jakub at gcc dot gnu.org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: marxin at gcc dot gnu.org @ 2020-03-24 9:11 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94296
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-03-24
Ever confirmed|0 |1
Known to work| |9.3.0
Target Milestone|--- |10.0
Priority|P3 |P2
Known to fail| |10.0
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug debug/94296] [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375
2020-03-24 9:11 [Bug debug/94296] New: [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375 marxin at gcc dot gnu.org
2020-03-24 9:11 ` [Bug debug/94296] " marxin at gcc dot gnu.org
@ 2020-03-24 10:55 ` jakub at gcc dot gnu.org
2020-03-25 8:59 ` jakub at gcc dot gnu.org
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu.org @ 2020-03-24 10:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94296
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This is yet another test that should be dg-skip-if -fcompare-debug and
-fno-asynchronous-unwind-tables.
The code is different depending on the __GCC_HAVE_DWARF2_CFI_ASM macro, which
is dependent on whether -g -fno-asynchronous-unwind-tables is present or not.
$ ./cc1 -quiet -g -fno-asynchronous-unwind-tables -dD -E /dev/null | grep CFI
#define __GCC_HAVE_DWARF2_CFI_ASM 1
$ ./cc1 -quiet -g0 -fno-asynchronous-unwind-tables -dD -E /dev/null | grep CFI
$ ./cc1 -quiet -g -gtoggle -fno-asynchronous-unwind-tables -dD -E /dev/null |
grep CFI
$ ./cc1 -quiet -g -fasynchronous-unwind-tables -dD -E /dev/null | grep CFI
#define __GCC_HAVE_DWARF2_CFI_ASM 1
$ ./cc1 -quiet -g0 -fasynchronous-unwind-tables -dD -E /dev/null | grep CFI
#define __GCC_HAVE_DWARF2_CFI_ASM 1
$ ./cc1 -quiet -g -gtoggle -fasynchronous-unwind-tables -dD -E /dev/null | grep
CFI
#define __GCC_HAVE_DWARF2_CFI_ASM 1
This macro is predefined when code should use .cfi_* directives in inline asm,
which is not when the assembler doesn't support them obviously, but otherwise
either when -fasynchronous-unwind-tables is on, or when -g is on. If neither
is on, neither .eh_frame nor .debug_frame will be emitted and thus the .cfi*
directives are undesirable.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug debug/94296] [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375
2020-03-24 9:11 [Bug debug/94296] New: [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375 marxin at gcc dot gnu.org
2020-03-24 9:11 ` [Bug debug/94296] " marxin at gcc dot gnu.org
2020-03-24 10:55 ` jakub at gcc dot gnu.org
@ 2020-03-25 8:59 ` jakub at gcc dot gnu.org
2020-03-25 10:41 ` cvs-commit at gcc dot gnu.org
2020-03-25 10:42 ` jakub at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu.org @ 2020-03-25 8:59 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94296
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Though, the testcase doesn't fail even with -fno-asynchronous-unwind-tables
-fcompare-debug -fexceptions, , so I don't see how one can reproduce it in make
check, even
make check-gcc
RUNTESTFLAGS='--target_board=unix/-fcompare-debug/-fno-asynchronous-unwind-tables/-fno-exceptions
dg.exp=cleanup-13.c'
is fine. So, I think this test isn't even a candidate for dg-skip-if, perhaps
just a comment that the test isn't -fcompare-debug compatible with those and
those options because...
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug debug/94296] [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375
2020-03-24 9:11 [Bug debug/94296] New: [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375 marxin at gcc dot gnu.org
` (2 preceding siblings ...)
2020-03-25 8:59 ` jakub at gcc dot gnu.org
@ 2020-03-25 10:41 ` cvs-commit at gcc dot gnu.org
2020-03-25 10:42 ` jakub at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-03-25 10:41 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94296
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:780f1cfd8eef90f6f5ea84cf58aa97e07c0c2aa1
commit r10-7374-g780f1cfd8eef90f6f5ea84cf58aa97e07c0c2aa1
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Mar 25 11:41:17 2020 +0100
testsuite: Mention cleanup-13.c test is incompatible with -fcompare-debug
[PR94296]
As this test produces different code depending on whether
__GCC_HAVE_DWARF2_CFI_ASM macro is defined or not, it is inherently
incompatible with -fcompare-debug, as with
-fcompare-debug -fno-asynchronous-unwind-tables -fno-exceptions
the macro is defined only in the -g case and not otherwise.
The purpose of the macro is to tell when the compiler is emitting
.cfi* directives itself and thus it is desirable that user code uses them
in
inline asm as well, so I think it is fine the way it is.
As -fexceptions makes the test pass even in that case because it emits
.cfi* directives, the test actually doesn't FAIL even with
make check-gcc
RUNTESTFLAGS='--target_board=unix/-fcompare-debug/-fno-asynchronous-unwind-tables/-fno-exceptions
dg.exp=cleanup-13.c'
so the intent of this patch is help Martin and others who do run gcc tests
out of the testsuite with random compiler flags to find out that this is a
known issue.
2020-03-25 Jakub Jelinek <jakub@redhat.com>
PR debug/94296
* gcc.dg/cleanup-13.c: Add a comment that the test is not
-fcompare-debug compatible with certain other options.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug debug/94296] [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375
2020-03-24 9:11 [Bug debug/94296] New: [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375 marxin at gcc dot gnu.org
` (3 preceding siblings ...)
2020-03-25 10:41 ` cvs-commit at gcc dot gnu.org
@ 2020-03-25 10:42 ` jakub at gcc dot gnu.org
4 siblings, 0 replies; 6+ messages in thread
From: jakub at gcc dot gnu.org @ 2020-03-25 10:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94296
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Added comment to testcase.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-03-25 10:42 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-24 9:11 [Bug debug/94296] New: [10 Regression] gcc: error: gcc/testsuite/gcc.dg/cleanup-13.c: ‘-fcompare-debug’ failure (length) since r10-4482-gaea86742ce396375 marxin at gcc dot gnu.org
2020-03-24 9:11 ` [Bug debug/94296] " marxin at gcc dot gnu.org
2020-03-24 10:55 ` jakub at gcc dot gnu.org
2020-03-25 8:59 ` jakub at gcc dot gnu.org
2020-03-25 10:41 ` cvs-commit at gcc dot gnu.org
2020-03-25 10:42 ` jakub at gcc dot gnu.org
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).