From: Alexandre Oliva <aoliva@redhat.com>
To: joern.rennecke@st.com
Cc: ac131313@cygnus.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: Thu, 09 May 2002 21:54:00 -0000 [thread overview]
Message-ID: <oradr8bo2t.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <3CD82502.C3A8695C@st.com>
On May 7, 2002, Joern Rennecke <joern.rennecke@st.com> wrote:
> 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?
> P.S.: It is not trivial to make gcc emit different register numbers
> for different sizes, but for prologue cfi, that can be done by
> attaching a REG_FRAME_RELATED_EXPR note referring to a different
> register number when emitting the prologue.
But under this design, if we moved to a more efficient exception
handling mechanism, how would throw() know whether to restore the
SHcompact or the SHmedia register before returning to the exception
landing pad?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-05-10 4:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 10:48 Joern Rennecke
2002-04-30 12:11 ` 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 9:06 ` gdb/sh-tdep.c: need to eliminate target-dependent static variables Joern Rennecke
2002-05-03 22:21 ` SH5 compact register numbering in gcc -> gdb interface Alexandre Oliva
2002-05-07 7:57 ` Joern Rennecke
2002-05-07 9:41 ` Andrew Cagney
2002-05-07 12:00 ` Joern Rennecke
2002-05-07 12:04 ` Elena Zannoni
2002-05-07 15:13 ` Andrew Cagney
2002-05-09 14:43 ` SH5 compact register numbering in gcc -> gdb interface - include/elf/sh.h ? Joern Rennecke
2002-05-09 15:33 ` Elena Zannoni
2002-05-09 16:50 ` Andrew Cagney
2002-05-10 6:55 ` Joern Rennecke
2002-05-10 7:40 ` Andrew Cagney
2002-05-10 7:49 ` Joern Rennecke
2002-05-10 7:03 ` SH simulator register numbers: include/gdb/sim-sh.h Joern Rennecke
2002-06-11 10:19 ` Unreviewed patch: add include/gdb/sim-sh.h (Was: Re: SH simulator register numbers: include/gdb/sim-sh.h) Joern Rennecke
2002-06-11 14:53 ` Elena Zannoni
2002-05-10 3:09 ` SH5 compact register numbering in gcc -> gdb interface - include/elf/sh.h ? Joern Rennecke
2002-05-10 7:33 ` Andrew Cagney
2002-05-10 7:46 ` Joern Rennecke
2002-05-10 3:25 ` Joern Rennecke
2002-05-07 12:03 ` SH5 compact register numbering in gcc -> gdb interface Joern Rennecke
2002-05-09 21:54 ` Alexandre Oliva [this message]
2002-05-08 0:14 ` DWARFx ? .debug sections infos phi 4369
2002-05-08 1:36 ` Lars Brinkhoff
2002-05-08 1:53 ` phi 4369
2002-05-08 6:35 ` Petr Sorfa
2002-05-07 10:13 ` 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=oradr8bo2t.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=ac131313@cygnus.com \
--cc=bje@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=joern.rennecke@st.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