Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa/arm] Fix the types of ARM FPA registers
Date: Thu, 25 Mar 2004 17:05:00 -0000	[thread overview]
Message-ID: <20040325170521.GA32184@nevyn.them.org> (raw)
In-Reply-To: <200403251453.i2PErEWI026528@pc960.cambridge.arm.com>

On Thu, Mar 25, 2004 at 02:53:13PM +0000, Richard Earnshaw wrote:
> > This has apparently been broken for a while... build an arm-elf GDB, connect
> > to the simulator, and say 'print $f0'.  You get an internal error because
> > the virtual size is 8 but the raw size is 12, and we don't define
> > DEPRECATED_REGISTER_CONVERTIBLE.
> > 
> > I don't think any of the baggage is necessary any more.  We can simply
> > expose the correct type.  After this patch, we have:
> > 
> > (gdb) ptype $f0
> > type = builtin_type_arm_ext_littlebyte_bigword
> > (gdb) p sizeof($f0)
> > $1 = 12
> > (gdb) p $f0
> > $2 = 0
> > 
> > I also got to whack five deprecated methods.
> > 
> > No change in test results on arm-sim, and it fixes the internal error.  I
> > don't have any hard-FPA targets to try it on (all my Linux setups are
> > soft-FPA or soft-VFP).
> > 
> 
> I get a few testsuite differences, but these appear to be race conditions 
> of some sort, and not related to floating point values in any way.  No FP 
> tests change.

Thanks.  I've checked this in for HEAD/6.1.

Any differences in the threads tests are ignorable.  I have patches
locally that need a little more testing which will improve the
situation.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2004-03-25 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 22:26 Daniel Jacobowitz
2004-03-25 10:28 ` Richard Earnshaw
2004-03-25 14:53 ` Richard Earnshaw
2004-03-25 17:05   ` Daniel Jacobowitz [this message]

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=20040325170521.GA32184@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.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