diff options
author | Jakub Jelinek <jakub@redhat.com> | 2020-03-25 11:41:17 +0100 |
---|---|---|
committer | Jakub Jelinek <jakub@redhat.com> | 2020-03-25 11:41:17 +0100 |
commit | 780f1cfd8eef90f6f5ea84cf58aa97e07c0c2aa1 (patch) | |
tree | cb651c2ac951764e843eb46aae9d3f60833159bd /gcc/gimple-fold.c | |
parent | d5ad8ee04a78b576867fd78b2f25201ea6b4aae1 (diff) | |
download | gcc-780f1cfd8eef90f6f5ea84cf58aa97e07c0c2aa1.zip gcc-780f1cfd8eef90f6f5ea84cf58aa97e07c0c2aa1.tar.gz gcc-780f1cfd8eef90f6f5ea84cf58aa97e07c0c2aa1.tar.bz2 |
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.
Diffstat (limited to 'gcc/gimple-fold.c')
0 files changed, 0 insertions, 0 deletions