Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Richard.Earnshaw@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: ARM and virtual/raw registers
Date: Sun, 12 May 2002 08:41:00 -0000	[thread overview]
Message-ID: <3CDE8D2B.1060706@cygnus.com> (raw)
In-Reply-To: <200205121525.QAA02703@cam-mail2.cambridge.arm.com>

>  However, in this situation, 
>> > pseudo_rengo("r0") != regcache_regno("r0"), yet we effectively have
>> > 
>> > REGSITER_RAW_SIZE (pseudo_regno ("r0")) 
>> > and
>> > REGISTER_RAW_SIZE (regcache_regno ("r0"))
> 
>> 
>> Sorry, I still don't understand.  
> 
> 
> In my view of things, the domain of the result returned by pseudo_regno() 
> is
> 0..Num_pseudos,

Pseudo-registers occupy the space:

[NUM_REGS .. NUM_REGS+NUM_PSEUDO_REGS)

there isn't an overlap.

As I said, I'd like to have strongly typed ``struct pseudoreg *'' and 
``struct rawreg *''.  In the mean time, this numeric separation is the 
onlything we have.

> and the domain of regcache_regno() is
> 
> 0..NUM_REGS
> 
> But we have cases where the two functions return a different number for 
> the same register; more precisely, we might encounter the situation where
> 
> pseudo_regno ("int_reg0") == regcache_regno ("float_reg5")

That isn't correct.

Andrew




  reply	other threads:[~2002-05-12 15:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09  7:31 Richard Earnshaw
2002-05-09  9:45 ` Andrew Cagney
2002-05-09 10:01   ` Richard Earnshaw
2002-05-09 11:52     ` Andrew Cagney
2002-05-10  3:45       ` Richard Earnshaw
2002-05-10  7:48         ` Andrew Cagney
2002-05-10 12:07           ` Andrew Cagney
2002-05-11  7:05             ` Richard Earnshaw
2002-05-11 14:52               ` Andrew Cagney
2002-05-12  7:20                 ` Richard Earnshaw
2002-05-12  8:25                   ` Andrew Cagney
2002-05-12  8:30                     ` Richard Earnshaw
2002-05-12  8:51                       ` Andrew Cagney
2002-05-10  9:29       ` Richard Earnshaw
2002-05-10 11:42         ` Andrew Cagney
2002-05-11  6:16           ` Richard Earnshaw
2002-05-11 11:41           ` Richard Earnshaw
2002-05-11 13:36             ` Andrew Cagney
2002-05-12  7:11               ` Richard Earnshaw
2002-05-12  7:40                 ` Richard Earnshaw
2002-05-12  9:03                   ` Andrew Cagney
2002-05-12 11:31                     ` Andrew Cagney
2002-05-12  8:07                 ` Andrew Cagney
2002-05-12  8:25                   ` Richard Earnshaw
2002-05-12  8:41                     ` Andrew Cagney [this message]
2002-05-13  5:35                   ` Richard Earnshaw
2002-05-13  6:13                     ` Andrew Cagney
2002-05-13  6:18                       ` Richard Earnshaw
2002-05-09 10:08 ` Andrew Cagney
2002-05-09 10:36   ` 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=3CDE8D2B.1060706@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=Richard.Earnshaw@arm.com \
    --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