From: Michael Snyder <msnyder@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] arm_store_return_value, big-endian (take 2)
Date: Wed, 13 Nov 2002 11:55:00 -0000 [thread overview]
Message-ID: <3DD2AE18.C1D0E978@redhat.com> (raw)
In-Reply-To: <200211121014.gACAEtF31639@pc960.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
Richard Earnshaw wrote:
>
> > 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???!!!!
Oh, I see. Yes, it's no longer necessary. But if it's not so hard,
and you already see what's necessary, why not just do it instead of
ragging on me to do it? ;-)
This what you have in mind? Please just take it from here, I really
didn't intend to spend this much time and energy on it.
[-- Attachment #2: arm6.patch --]
[-- Type: text/plain, Size: 722 bytes --]
Index: arm-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/arm-tdep.c,v
retrieving revision 1.74
diff -p -r1.74 arm-tdep.c
*** arm-tdep.c 1 Nov 2002 21:21:49 -0000 1.74
--- arm-tdep.c 13 Nov 2002 19:48:21 -0000
*************** arm_store_return_value (struct type *typ
*** 2417,2424 ****
break;
}
}
! else
! write_register_bytes (ARM_A1_REGNUM, valbuf, TYPE_LENGTH (type));
}
/* Store the address of the place in which to copy the structure the
--- 2417,2424 ----
break;
}
}
! else
! write_register (ARM_A1_REGNUM, unpack_long (type, valbuf);
}
/* Store the address of the place in which to copy the structure the
next prev parent reply other threads:[~2002-11-13 19:55 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
2002-11-13 11:55 ` Michael Snyder [this message]
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=3DD2AE18.C1D0E978@redhat.com \
--to=msnyder@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--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