Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: gdb@sources.redhat.com
Subject: Re: A matter of taste?
Date: Wed, 09 Jul 2003 14:10:00 -0000	[thread overview]
Message-ID: <jeisqbokq7.fsf@sykes.suse.de> (raw)
In-Reply-To: <20030709135543.GO12368@cygbert.vinschen.de> (Corinna Vinschen's message of "Wed, 9 Jul 2003 15:55:43 +0200")

Corinna Vinschen <vinschen@redhat.com> writes:

|> Hi,
|> 
|> I'm currently substituting a bunch of calls to REGISTER_RAW_SIZE.
|> Since REGISTER_RAW_SIZE should be removed entirely, I was wondering
|> how to do it most nicely.
|> 
|> What I don't quite get is the implementation of function register_size
|> in regcache.c.  It retrieves the size of the regsiter from the 
|> regcache and then checks twice(!) if that size equals REGISTER_RAW_SIZE.

The second check probabably should have been against
REGISTER_VIRTUAL_SIZE.

|> If I understand that correctly, a multi-arched target which got rid of
|> REGISTER_RAW_SIZE can't use register_size () since the REGISTER_RAW_SIZE
|> calls in register_size will raise an internal_error in
|> gdbarch_deprecated_register_raw_size().

If you don't define REGISTER_RAW_SIZE then it is defined to
generic_register_size, which uses TYPE_LENGTH.

|> What is that good for?  And what's the substitute for a target with
|> no REGISTER_RAW_SIZE implementation?

Just use register_size.  Works fine on m68k.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  parent reply	other threads:[~2003-07-09 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 13:55 Corinna Vinschen
2003-07-09 14:03 ` register_size question (was Re: A matter of taste?) Corinna Vinschen
2003-07-09 14:10 ` Andreas Schwab [this message]
2003-07-09 14:20   ` A matter of taste? Corinna Vinschen
2003-07-09 14:24   ` 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=jeisqbokq7.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb@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