From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Edmar <edmar@freescale.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
"rohitarulraj@freescale.com" <rohitarulraj@freescale.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Alan Modra <amodra@gmail.com>, Jakub Jelinek <jakub@redhat.com>,
<gdb@sourceware.org>
Subject: Re: [RFC: Patch, PR 60102] [4.9/4.10 Regression] powerpc fp-bit ices@dwf_regno
Date: Sun, 28 Sep 2014 22:23:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1409282316450.4971@tp.orcam.me.uk> (raw)
In-Reply-To: <53DFBA16.5060409@freescale.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
next prev parent reply other threads:[~2014-09-28 22:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 2:42 [RFC: Patch, PR 60102] [4.9/4.10 Regression] powerpc fp-bit ices at dwf_regno rohitarulraj
2014-07-22 7:28 ` rohitarulraj
2014-07-24 16:54 ` [RFC: Patch, PR 60102] [4.9/4.10 Regression] powerpc fp-bit ices@dwf_regno Ulrich Weigand
2014-07-31 18:23 ` rohitarulraj
2014-08-01 14:29 ` Ulrich Weigand
2014-08-01 18:04 ` rohitarulraj
2014-08-01 18:10 ` Jakub Jelinek
2014-08-01 18:21 ` rohitarulraj
2014-08-02 1:46 ` David Edelsohn
2014-08-04 10:25 ` Ulrich Weigand
2014-08-04 16:56 ` Edmar
2014-08-05 8:11 ` Jakub Jelinek
2014-08-05 10:44 ` rohitarulraj
2014-08-05 14:47 ` Edmar
2014-09-28 22:23 ` Maciej W. Rozycki [this message]
2014-09-29 9:44 ` Ulrich Weigand
2014-09-29 10:24 ` rohitarulraj
2014-09-29 17:26 ` Maciej W. Rozycki
2014-10-06 15:48 ` rohitarulraj
2014-10-08 18:09 ` Ulrich Weigand
2014-10-08 18:27 ` David Edelsohn
2014-10-08 19:47 ` Maciej W. Rozycki
2014-10-09 12:20 ` rohitarulraj
2014-10-09 13:40 ` Ulrich Weigand
2014-10-09 15:49 ` Maciej W. Rozycki
2014-10-11 14:49 ` Maciej W. Rozycki
2014-10-13 13:22 ` Ulrich Weigand
2014-10-13 17:39 ` David Edelsohn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.1.10.1409282316450.4971@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=amodra@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=edmar@freescale.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jakub@redhat.com \
--cc=rohitarulraj@freescale.com \
--cc=uweigand@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).