From: Andrew Cagney <cagney@gnu.org>
To: Andrew Cagney <cagney@gnu.org>, Mark Kettenis <kettenis@chello.nl>
Cc: Ulrich Weigand <weigand@i1.informatik.uni-erlangen.de>,
gdb-patches@sources.redhat.com, uweigand@de.ibm.com
Subject: Re: [PATCH] S/390 DWARF-2 CFI frame support
Date: Wed, 10 Dec 2003 17:14:00 -0000 [thread overview]
Message-ID: <3FD7548D.7080300@gnu.org> (raw)
In-Reply-To: <3FD0ABF9.4090201@gnu.org>
Mark,
This is really a question for you. If you want I can hack up the code
(although I don't know exactly when that would happen).
Andrew
> Hello,
>
> this patch adds support for DWARF-2 frame handling to the s390 backend.
>
> However, the DWARF-2 frame common code makes a couple of assumptions
> that are not valid on s390:
>
> - The return address column is not unwound into the specified register,
> only into the PC. On s390, it should be unwound into both.
>
> The patch below fixes this by unwinding into both register
> and PC if the return column corresponds to a GDB register.
>
> What does the CFI output look like here? (I'm mainly curious but it always helps to have concrete examples).
>
> For a variant of the PPC64 GCC I found:
>
> - return column pointed at the FSCR
> (which is stupid)
>
> - return column same-value as "LR" was implied
> (which is contrary to the DWARF2's example, and what you also encountered)
>
> this means that we've now got the following initial states all mapping onto "unspecified":
>
> - same value
> - unknown
> - (for SP_REGNUM) it's the CFA (but is it one frame out?)
> - (for return column) it's the LR
>
> I'm wondering if it would be easier, here to "give up". Throw the whole problem back at the architecture vis:
>
> - initialize unwind table using per OSABI (?) method
>
> - update the unwind table using the CFI initialize info
>
> - update the unwind table using the PC's CFI unwind info
>
> - if after all this a register is still unspecified, we complain
> (btw, the compaint is only ment to appear once but apparently appears repeatedly?).
>
> Thoughts for the moment on the theory? Mark?
>
> It should also open the way for the elimination of SP_REGNUM and PC_REGNUM from this file (ya!).
>
> As for an interface, the <ARCH>_gdbarch_init code could something like:
>
> dwarf2_frame_add_sniffer (gdbarch, (*<ARCH>_dwarf2_cfi_init) (struct cfi_table *table));
>
> (but with better names :-).
>
> Andrew
next prev parent reply other threads:[~2003-12-10 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 20:09 Ulrich Weigand
2003-12-04 22:47 ` Jim Blandy
2003-12-05 0:49 ` Richard Henderson
2003-12-05 1:04 ` Andrew Cagney
2003-12-05 1:44 ` Richard Henderson
2003-12-05 2:03 ` Ulrich Weigand
2003-12-05 2:11 ` Richard Henderson
2003-12-05 2:16 ` Ulrich Weigand
2003-12-05 2:13 ` Daniel Jacobowitz
2003-12-05 2:19 ` Ulrich Weigand
2003-12-05 16:02 ` Andrew Cagney
2003-12-05 17:54 ` Ulrich Weigand
2003-12-10 17:14 ` Andrew Cagney [this message]
2003-12-10 18:52 ` Ulrich Weigand
2003-12-12 17:43 ` Mark Kettenis
2003-12-13 15:32 ` Ulrich Weigand
2003-12-14 15:23 ` Mark Kettenis
2003-12-14 16:40 ` Andrew Cagney
2003-12-14 17:16 ` Mark Kettenis
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=3FD7548D.7080300@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--cc=uweigand@de.ibm.com \
--cc=weigand@i1.informatik.uni-erlangen.de \
/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