Re: Remaining 7.5 regressions (Re: [ARM, commit, RFA 7.5] Fix HW breakpoints on unaligned addresses)

[Sergio Durigan Junior <sergiodj@redhat.com>]

On Wednesday, August 01 2012, Ulrich Weigand wrote:

> Joel Brobecker wrote:

>> > In general, what's the timeline for 7.5?  I've noticed a couple of
>> > other test case regressions when testing the branch on ARM, s390,
>> > and Cell ...
>> 
>> The branch was created on July 17th, and the target date for release
>> creation is 2 weeks after that, which would have been today. I thought
>> there was still one open issue, but the release page says we're clean
>> (except for your issue).
>
> In addition to the failures fixed by the above patches, I'm still seeing:
>
> - Failures in gdb.base/pc-fp.exp on various platforms, as described here:
>   http://sourceware.org/ml/gdb-patches/2012-07/msg00823.html
>   (just an output formatting issue)

This patch will probably go in tomorrow when I wake up, if Pedro
approves it.  It is also simple enough to be committed to 7.5.

> - Failures in gdb.mi/mi-var-rtti.exp on various platforms, see:
>   http://sourceware.org/ml/gdb-patches/2012-07/msg00458.html
>   (seems to be a bug in the test case)

I see them also on s390x as you pointed out, but not on ppc64.

> - Failures in gdb.threads/watchpoint-fork.exp on ARM and PowerPC.
>   This looks like a pre-existing bug that hardware watchpoints are not
>   handled correctly across forks, which is now exposed since a test
>   case for this scenario was added.

I seem some failures on s390x as well:

    +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: breakpoint after the second fork (timeout)
    +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: watchpoint after the second fork
    +FAIL: gdb.threads/watchpoint-fork.exp: child: singlethreaded: finish

> - Some new C++ regressions on ARM / s390x (could be compiler issues?)

Could you tell which C++ regressions are those?  I see this on
PPC64/s390x:

-PASS: gdb.cp/inherit.exp: print g_vB (FIXME v3 vtbl ptr)
-PASS: gdb.cp/inherit.exp: print g_vC (FIXME v3 vtbl ptr)
+FAIL: gdb.cp/inherit.exp: print g_vB
+FAIL: gdb.cp/inherit.exp: print g_vC
...
-PASS: gdb.cp/inherit.exp: print g_vE (FIXME v3 vtbl ptr)
+FAIL: gdb.cp/inherit.exp: print g_vE

-PASS: gdb.cp/virtbase.exp: print *this
+FAIL: gdb.cp/virtbase.exp: print *this
...
-PASS: gdb.cp/virtbase.exp: print *(D *) e
+FAIL: gdb.cp/virtbase.exp: print *(D *) e


I am investigating the last two (virtbase.exp), since I had a brief
discussion with Jan about the inherit.exp one and he mentioned it is
probably a compiler issue (though I could not confirm yet).

> - Failures in various core file tests on PowerPC (needs investigation)

I am not seeing this on ppc64 RHEL 6.3.

> - Failures in gdb.threads/siginfo-threads.exp on s390 (needs investigation)

Fully passing for me on s390x RHEL 6.3.

> - Failures in gdb.dwarf2/dw2-icc-opaque.exp on SPU and s390 (likewise)

I can confirm on s390x, and I am also seeing on ppc64.

>> The easiest for me would probably to create it on Friday, assuming
>> that we don't discover something new by then.
>
> I'll see what I can track down and fix until Friday.  Sorry for starting
> my test series a bit late this time ...

Please keep me informed if it is possible, I am also tackling some
regressions as you are.

Thanks,

-- 
Sergio