Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Michael Snyder <msnyder@redhat.com>
Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com,
	cagney@redhat.com, kevinb@redhat.com
Subject: Re: [RFA] arm_store_return_value, big-endian (take 2)
Date: Tue, 12 Nov 2002 02:15:00 -0000	[thread overview]
Message-ID: <200211121014.gACAEtF31639@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Mon, 11 Nov 2002 10:49:32 PST." <3DCFFBBC.715EB616@redhat.com>

> Richard Earnshaw wrote:
> > 
> > > Richard Earnshaw wrote:
> > > >
> > > > > Richard Earnshaw wrote:
> > > > > >
> > > > > > Leaving asside the issue of the correctness of write_register_bytes (note
> > > > > > to self, must finish of my register patches), I don't think this is
> > > > > > correct -- in fact, I think it's also wrong for little-endian as well.
> > > > > >
> > > > > > What should happen is that the smaller-than-word value should be
> > > > > > zero/sign-extended to 32 bits and then the whole thing stored in A1_REGNUM.
> > > > >
> > > > > Ah, thanks.  OK, how about this?
> > > > >
> > > > > 2002-11-06  Michael Snyder  <msnyder@redhat.com>
> > > > >
> > > > >       * arm-tdep.c (arm_store_return_value): Handle offset of
> > > > >       small types on big-endian machines.
> > > >
> > > > And for little-endian?
> > >
> > > It already works for little-endian.  I've tested this with
> > > arm-sim, arm-sim/-mbig-endian, and arm-sim/-mthumb.
> > 
> > But it's not zero/sign extending properly for little-endian, so garbage is
> > remaining in the top part of A1
> 
> Ah; well, I didn't make it any worse!  ;-)
> Can I leave that detail for someone else, and just
> submit this minor improvement?

Given that to fix this for little-endian as well means that you just have 
to *remove* the endianness test from your patch, why is that so hard???!!!!

Also, you should add a comment at this point explaining that we want to 
extend the value into the whole register.

R.


  reply	other threads:[~2002-11-12 10:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 16:27 Michael Snyder
2002-11-07 10:26 ` Richard Earnshaw
2002-11-07 19:19   ` Michael Snyder
2002-11-08  1:57     ` Richard Earnshaw
2002-11-08 11:37       ` Michael Snyder
2002-11-09  3:55         ` Richard Earnshaw
2002-11-11 17:15           ` Michael Snyder
2002-11-12  2:15             ` Richard Earnshaw [this message]
2002-11-13 11:55               ` Michael Snyder
2002-11-14  1:50                 ` Richard Earnshaw

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=200211121014.gACAEtF31639@pc960.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=cagney@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@redhat.com \
    --cc=msnyder@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