This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: [RFC: Patch, PR 60102] [4.9/4.10 Regression] powerpc fp-bit ices at dwf_regno
- From: "Maciej W. Rozycki" <macro at codesourcery dot com>
- To: Edmar <edmar at freescale dot com>
- Cc: Ulrich Weigand <uweigand at de dot ibm dot com>, David Edelsohn <dje dot gcc at gmail dot com>, "rohitarulraj at freescale dot com" <rohitarulraj at freescale dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Alan Modra <amodra at gmail dot com>, Jakub Jelinek <jakub at redhat dot com>, <gdb at sourceware dot org>
- Date: Sun, 28 Sep 2014 23:23:18 +0100
- Subject: Re: [RFC: Patch, PR 60102] [4.9/4.10 Regression] powerpc fp-bit ices at dwf_regno
- Authentication-results: sourceware.org; auth=none
- References: <201408041025 dot s74APFJK000841 at d06av02 dot portsmouth dot uk dot ibm dot com> <53DFBA16 dot 5060409 at freescale dot com>
On Mon, 4 Aug 2014, Edmar wrote:
> Committed on trunk, revision 213596
> Committed on 4.9 branch, revision 213597
This change regressed GDB for e500v2 multilibs, presumably because it
does not understand the new DWARF register numbers and does not know how
to map them to hardware registers. Here's the full list of regressions
observed:
FAIL: gdb.base/store.exp: var double l; print old l, expecting -1
FAIL: gdb.base/store.exp: var double l; print old r, expecting -2
FAIL: gdb.base/store.exp: var double l; print incremented l, expecting 2
FAIL: gdb.base/store.exp: var doublest l; print old l, expecting -1
FAIL: gdb.base/store.exp: var doublest l; print old r, expecting -2
FAIL: gdb.base/store.exp: var doublest l; print new l, expecting 4
FAIL: gdb.base/store.exp: var doublest l; print incremented l, expecting 2
FAIL: gdb.base/store.exp: upvar double l; print old l, expecting -1
FAIL: gdb.base/store.exp: upvar double l; print old r, expecting -2
UNRESOLVED: gdb.base/store.exp: upvar double l; set l to 4
UNRESOLVED: gdb.base/store.exp: upvar double l; print new l, expecting 4
FAIL: gdb.base/store.exp: upvar doublest l; print old l, expecting -1
FAIL: gdb.base/store.exp: upvar doublest l; print old r, expecting -2
UNRESOLVED: gdb.base/store.exp: upvar doublest l; set l to 4
UNRESOLVED: gdb.base/store.exp: upvar doublest l; print new l, expecting 4
These tests all used to score a PASS status. Do you plan to address this
problem anyhow?
Maciej