public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@st.com>
To: ac131313@cygnus.com
Cc: aoliva@redhat.com, ezannoni@redhat.com, gcc@gcc.gnu.org,
	gdb@sources.redhat.com, bje@redhat.com
Subject: Re: SH5 compact register numbering in gcc -> gdb interface
Date: Tue, 07 May 2002 12:03:00 -0000	[thread overview]
Message-ID: <3CD823D1.FC1E3717@st.com> (raw)
In-Reply-To: <3CD803BC.5060900@cygnus.com>

ac131313@cygnus.com wrote:
> Humor me here.
> 
> How do you use dwarf2 cfi to unwind a compact register (saved on the
> stack) back to a media register?  In addition to the address of the
> saved register you'll need to know that only part of the register was
> saved. Does CFI describe this?

With the proposed numbering change (2nd revision), we get different
numbers to describe compact an media registers.  So when only the lower
32 bits are saved, gcc can use the SHcompact register number to describe
this.

N.B., the upper 32 bits of the register are actually overwritten in the
process.  The restore from the stack sign-extends from bit 31.  The caller
is responsible to make sure that no 64 bit value is live in the register.	

-- 
--------------------------
SuperH
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330

  reply	other threads:[~2002-05-07 19:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-30 10:53 Joern Rennecke
2002-04-30 12:30 ` Joern Rennecke
2002-05-01 17:55   ` Elena Zannoni
2002-05-02  3:13     ` Joern Rennecke
2002-05-01 17:52 ` Elena Zannoni
2002-05-02  5:06   ` Joern Rennecke
2002-05-03 22:21     ` Alexandre Oliva
2002-05-07  7:57       ` Joern Rennecke
2002-05-07 10:12         ` Andrew Cagney
2002-05-07 12:03           ` Joern Rennecke [this message]
2002-05-07 12:09             ` Elena Zannoni
2002-05-07 15:13             ` Andrew Cagney
2002-05-09 14:53               ` SH5 compact register numbering in gcc -> gdb interface - include/elf/sh.h ? Joern Rennecke
2002-05-09 15:42                 ` Elena Zannoni
2002-05-09 18:22                   ` Andrew Cagney
2002-05-10  7:33                     ` Joern Rennecke
2002-05-10  7:52                       ` Andrew Cagney
2002-05-10  8:38                         ` Joern Rennecke
2002-05-10  4:14                   ` Joern Rennecke
2002-05-10  7:49                     ` Andrew Cagney
2002-05-10  7:53                       ` Joern Rennecke
2002-05-10  4:18                   ` Joern Rennecke
2002-05-07 12:04           ` SH5 compact register numbering in gcc -> gdb interface Joern Rennecke
2002-05-09 22:53             ` Alexandre Oliva
2002-05-08  0:56         ` DWARFx ? .debug sections infos phi 4369
2002-05-08  1:57           ` Lars Brinkhoff
2002-05-08  2:43             ` phi 4369
2002-05-08  7:34               ` Petr Sorfa
2002-05-07 10:19     ` SH5 compact register numbering in gcc -> gdb interface 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=3CD823D1.FC1E3717@st.com \
    --to=joern.rennecke@st.com \
    --cc=ac131313@cygnus.com \
    --cc=aoliva@redhat.com \
    --cc=bje@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).