From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jakub Jelinek <jakub@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Fix sparc-*-linux register fetching/storing
Date: Mon, 12 Nov 2001 10:39:00 -0000 [thread overview]
Message-ID: <3C02795A.9000104@cygnus.com> (raw)
In-Reply-To: <20011125115446.A15038@nevyn.them.org>
>
> Well, regcache_collect is the only approved interface to the contents
> of registers[] for one thing. It would also prevent the need for the
> cast (although you'd have to clear the upper half of the variable
> first and make sure to stuff it into the low bytes since we're
> big-endian. Ew.).
>
> Andrew? Do we need to have a regcache_collect_core_addr, to sign
> extend and shift appropriately for each architecture?
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.
Andrew
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.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 09:18:00 -0000 [thread overview]
Message-ID: <3C02795A.9000104@cygnus.com> (raw)
Message-ID: <20011126091800.SaKyIjlppcj3K_CfeWibz7Fz5VERhAhwYVoza1Zjj30@z> (raw)
In-Reply-To: <20011125115446.A15038@nevyn.them.org>
>
> Well, regcache_collect is the only approved interface to the contents
> of registers[] for one thing. It would also prevent the need for the
> cast (although you'd have to clear the upper half of the variable
> first and make sure to stuff it into the low bytes since we're
> big-endian. Ew.).
>
> Andrew? Do we need to have a regcache_collect_core_addr, to sign
> extend and shift appropriately for each architecture?
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.
Andrew
next prev parent reply other threads:[~2001-11-26 17:18 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 [this message]
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
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=3C02795A.9000104@cygnus.com \
--to=ac131313@cygnus.com \
--cc=drow@mvista.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