C++ debug info regressions in 4.5

Bug #649067 reported by Ulrich Weigand
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro GCC
Fix Released
Medium
Ulrich Weigand
4.5
Fix Released
Medium
Ulrich Weigand

Bug Description

Running the GDB test suite against Linaro GCC 4.5 results in nearly 150 C++ test failures; with Linaro GCC 4.4 we see only 5.

Nearly all of those failures are caused by the problem described in this upstream bug report:

[4.5 Regression] in-class func-ptr type parameter has unspecified DW_AT_type
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43628

which actually is already fixed in both mainline and the 4.5 branch, but the fix is not yet in GCC 4.5.1

In addition, two further failures are due to this bug:

pointer type information lost in debuginfo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45088

which -as of now- does not yet have an upstream fix.

All these are platform-independent problems.

Revision history for this message
Michael Hope (michaelh1) wrote :

Ulrich, can you confirm that this was fixed with the GCC 4.5.1+svn merge done for Linaro GCC 4.5-2010.10-0 please?

Revision history for this message
Ulrich Weigand (uweigand) wrote :

The patch to fix PR 42638 is now present in GCC Linaro 4.5. I've not yet run the test suite ...

Revision history for this message
Ulrich Weigand (uweigand) wrote :

Testing on x86 confirms that most of the regressions are now gone due to the PR 42638 fix.

The following regressions remain; as mentioned in the bug report, these are due to bug PR 45088:
FAIL: gdb.cp/class2.exp: p acp->c1
FAIL: gdb.cp/class2.exp: p acp->c2
If you prefer, we can open a second bug to track these. (There is no fix available upstream yet.)

In addition, I'm now seeing yet another failure:
FAIL: gdb.cp/temargs.exp: test value of P in inner_m
Not sure yet what causes this one.

Revision history for this message
Michael Hope (michaelh1) wrote :

Split the second set into #662324. Closing this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.