Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
	Richard.Earnshaw@arm.com, gdb@sources.redhat.com
Subject: Re: REGISTER_BYTE() and pseudos
Date: Wed, 15 May 2002 10:46:00 -0000	[thread overview]
Message-ID: <200205151745.SAA16914@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 15 May 2002 13:35:14 EDT." <15586.40018.722458.418880@localhost.redhat.com>


> Yeah, I was going to chime in, but I am behind on this thread.
> Richard, look at the sh-tdep.c file. I checked in the sh5 work.  It
> still needs another round of cleaning but ti should pretty much all be
> there.

OK, I'll have another look.  

The bit I'm worried about though is if we call something like 
generic_get_saved_register for a pseudo and we hit a call_dummy frame.  
The code in there goes:

      if (PC_IN_CALL_DUMMY (frame->pc, frame->frame, frame->frame))
        {
          if (lval)             /* found it in a CALL_DUMMY frame */
            *lval = not_lval;
          if (raw_buffer)
            memcpy (raw_buffer,
                    generic_find_dummy_frame (frame->pc, frame->frame) +
                    REGISTER_BYTE (regnum),
                    REGISTER_RAW_SIZE (regnum));
          return;

Which will try to look up the pseudo in the buffer even if it isn't there.


  reply	other threads:[~2002-05-15 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15  9:36 Richard Earnshaw
2002-05-15 10:06 ` Andrew Cagney
2002-05-15 10:35   ` Elena Zannoni
2002-05-15 10:46     ` Richard Earnshaw [this message]
2002-05-15 11:46       ` Elena Zannoni
2002-05-15 11:08     ` Richard Earnshaw
2002-05-15 11:45       ` Elena Zannoni
2002-05-15 13:01       ` 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=200205151745.SAA16914@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=ac131313@cygnus.com \
    --cc=ezannoni@redhat.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