On Thu, May 30, 2013 at 1:40 AM, Andreas Schwab <sch...@linux-m68k.org> wrote:
> Rainer Orth <r...@cebitec.uni-bielefeld.de> writes:
>
>> And why do you add -gdwarf-2 in dg-options? AFAICS all tests in
>> gcc.dg/debug/dwarf2 are built with -gdwarf-2 anyway.
>
> Do they? Not here.
>
> Executing on host: /daten/aranym/gcc/gcc-20130530/Build/gcc/xgcc
> -B/daten/aranym/gcc/gcc-20130530/Build/gcc/
> /daten/aranym/gcc/gcc-20130530/gcc/testsuite/gcc.dg/debug/dwarf2/discriminator.c
> -fno-diagnostics-show-caret -fdiagnostics-color=never -ansi
> -pedantic-errors -O0 -ffat-lto-objects -ffat-lto-objects -ffat-lto-objects -S
> -o discriminator.s (timeout = 300)
> spawn /daten/aranym/gcc/gcc-20130530/Build/gcc/xgcc
> -B/daten/aranym/gcc/gcc-20130530/Build/gcc/
> /daten/aranym/gcc/gcc-20130530/gcc/testsuite/gcc.dg/debug/dwarf2/discriminator.c
> -fno-diagnostics-show-caret -fdiagnostics-color=never -ansi -pedantic-errors
> -O0 -ffat-lto-objects -ffat-lto-objects -ffat-lto-objects -S -o
> discriminator.s
> PASS: gcc.dg/debug/dwarf2/discriminator.c (test for excess errors)
> FAIL: gcc.dg/debug/dwarf2/discriminator.c scan-assembler loc [0-9] 11 [0-9](
> is_stmt [0-9])?\n
> FAIL: gcc.dg/debug/dwarf2/discriminator.c scan-assembler loc [0-9] 11 [0-9](
> is_stmt [0-9])? discriminator 2\n
> FAIL: gcc.dg/debug/dwarf2/discriminator.c scan-assembler loc [0-9] 11 [0-9](
> is_stmt [0-9])? discriminator 1\n
That's weird cause in dwarf2.exp:
# If a testcase doesn't have special options, use these.
global DEFAULT_CFLAGS
if ![info exists DEFAULT_CFLAGS] then {
set DEFAULT_CFLAGS " -ansi -pedantic-errors -gdwarf-2"
}
But anyway, shall I add the -gdwarf-2 option back to discriminator.c?
Dehao
>
> Andreas.
>
> --
> Andreas Schwab, sch...@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
