This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
The related regressions, just with arm-none-eabi GCC and the default multilib:
PASS -> FAIL: default/gdb.sum:gdb.base/code-expr.exp: (@code signed long) PASS -> FAIL: default/gdb.sum:gdb.base/code-expr.exp: (@data signed long) PASS -> FAIL: default/gdb.sum:gdb.base/code-expr.exp: (signed long @code) PASS -> FAIL: default/gdb.sum:gdb.base/code-expr.exp: (signed long @data) PASS -> FAIL: default/gdb.sum:gdb.base/cvexpr.exp: (const signed long) PASS -> FAIL: default/gdb.sum:gdb.base/cvexpr.exp: (signed long const) PASS -> FAIL: default/gdb.sum:gdb.base/cvexpr.exp: (signed long volatile) PASS -> FAIL: default/gdb.sum:gdb.base/cvexpr.exp: (volatile signed long)
PASS -> FAIL: default/gdb.sum:gdb.cp/exception.exp: backtrace after first catch PASS -> FAIL: default/gdb.sum:gdb.cp/exception.exp: backtrace after first throw PASS -> FAIL: default/gdb.sum:gdb.cp/exception.exp: backtrace after second catch PASS -> FAIL: default/gdb.sum:gdb.cp/exception.exp: backtrace after second throw
PASS -> FAIL: default/gdb.sum:gdb.cp/namespace.exp: print X PASS -> FAIL: default/gdb.sum:gdb.cp/namespace.exp: print cX
Some warnings are in order. First, this is probably going to really slow down large C++ applications, because we no longer use DW_AT_MIPS_linkage_name as generated from the compiler. We essentially build this name during DIE reading.
We need to quantify the impact on a couple of C++ code bases, I think.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |