RFA/RFC: Change Sparc64 gdb.asm tests to use -gdwarf2 instead of -gstabs
Michael Chastain
mec.gnu@mindspring.com
Thu Jul 29 23:38:00 GMT 2004
Mark Kettenis <kettenis@chello.nl> wrote:
> Not all right! Nick, did you actually test this patch?
Yes, he did.
If you keep reading the thread, you can see that I asked Nick to
test with "dwarf-2" and "stabs+", and Nick actually tested with
"dwarf2" and "stabs+" (which source.exp translates to "stabs").
But it looks like Nick's tests did not actually test. :(
> The subject of this thread is making sparc64 use -gdwarf2 instead of
> -gstabs, but > the patch changes it to -gdwarf-2 (note the extra
> dash). This isn't accepted by gas on my OpenBSD/amd64 and
> OpenBSD/sparc64 systems, and AFAICT it isn't accepted by the current
> gas from CVS either.
Hmmm. Ick. You're right. Nick tested with "dwarf2" on the command
line, but the patch says "dwarf-2" embedded in the code. And
the assembler spells "dwarf2" differently from gcc, which spells
it "dwarf-2". And to make matters more confusing, old assemblers
do not understand "stabs+", but as 2.15 does support stabs+ with
new extensions.
For dwarf-2, I'd like to spell it the same way everywhere, and
translate it at the last moment for binutils. That way, people
can run the test suite with:
make check RUNTESTFLAGS="--target_board unix/gdb:debug_flags=dwarf-2"
... and will get dwarf-2 with all languages.
Like this:
# The GNU assembler spells dwarf-2 as "dwarf2".
if { ${debug-flags} == "-gdwarf-2" } then {
set debug-flags "-gdwarf2"
}
Mark, does that work on your system?
I'll test it on my system later tonight.
Michael C
More information about the Gdb-patches
mailing list