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 <ja...@gcc.gnu.org>: https://gcc.gnu.org/g:780f1cfd8eef90f6f5ea84cf58aa97e07c0c2aa1 commit r10-7374-g780f1cfd8eef90f6f5ea84cf58aa97e07c0c2aa1 Author: Jakub Jelinek <ja...@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 <ja...@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.
