From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jakub Jelinek <jakub@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix sparc-*-linux register fetching/storing
Date: Mon, 26 Nov 2001 12:43:00 -0000 [thread overview]
Message-ID: <20011126154347.A8899@nevyn.them.org> (raw)
Message-ID: <20011126124300.XiERSxi2JbdBoqQNmM1D96sca4MFVI8pkBAQj5RAUH4@z> (raw)
In-Reply-To: <3C02A761.4030003@cygnus.com>
On Mon, Nov 26, 2001 at 03:34:41PM -0500, Andrew Cagney wrote:
>
> >>That sounds like overkill. If you need to be doing sign/zero extension
> >>stuff then I'd be looking at explicit calls to extract_signed_integer()
> >>and/or extract_unsigned_integer() in the nat code.
> >>
> >>A sequence like:
> >>
> >>void *buf = alloca (MAX_REGISTER_RAW_SIZE);
> >>regcache_collect (my reg, buf);
> >>LONGEST val = extract_unsigned_integer (buf, REGISTER_RAW_SIZE(my reg));
> >>store_unsigned_integer (dest, dest size, val);
> >>
> >>should insulate it from the current problems.
> >
> >
> >But won't we want this absolutely every time we extract a CORE_ADDR?
> >And for that matter, I'm talking about getting a target memory address
> >out of a register; is store_*signed_integer right for that? Is there
> >an extract_pointer or so?
>
> In *-nat.c? Now I'm confused :-)
>
> Doesn't the *-nat.c file just copy raw register bytes between the
> regcache and the /proc or ptrace() interface? The only complication I
> could see is if someone used 32 bit ptrace calls to get the values for a
> regcache that had space for 64 bit registers - the above code snipit
> would handle that.
>
> The reason for suggesting extract/store signed/unsigned integer is that
> they have clear, machine independant, semantics that work on
> uninterpreted (well apart from assuming they are integers :-) bytes.
Well, remember that we can't cast things to (CORE_ADDR *) reliably.
With --enable-64-bit-bfd, that has a tendency to turn into a 'long long *'.
What was happening was reading $sp out of the regcache, and then
passing it to target_read_memory. If this were MIPS, I think we'd have
to sign extend there, for "correctness". We'd eventually truncate it
back down with a cast in infptrace.c, though.
I just don't like duplicating that above code sequence everywhere we
get a pointer out of a register into a CORE_ADDR. It seems like a very
frequent operation, in nat or in tdep.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-11-26 12:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-10 9:20 Jakub Jelinek
2001-11-10 13:03 ` Daniel Jacobowitz
2001-11-10 16:27 ` Jakub Jelinek
2001-11-10 16:35 ` Daniel Jacobowitz
2001-11-10 16:41 ` Jakub Jelinek
2001-11-10 16:42 ` Daniel Jacobowitz
2001-11-12 10:39 ` Andrew Cagney
2001-11-26 9:18 ` Andrew Cagney
2001-11-26 12:04 ` Daniel Jacobowitz
2001-11-12 18:40 ` Daniel Jacobowitz
2001-11-26 12:34 ` Andrew Cagney
2001-11-12 19:11 ` Andrew Cagney
2001-11-13 8:19 ` Daniel Jacobowitz [this message]
2001-11-26 12:43 ` Daniel Jacobowitz
2001-11-26 13:19 ` Andrew Cagney
2001-11-13 8:28 ` Andrew Cagney
2001-11-26 9:08 ` Andrew Cagney
2001-11-12 10:04 ` Andrew Cagney
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=20011126154347.A8899@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jakub@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