From: Daniel Jacobowitz <drow@false.org>
To: Jan Beulich <JBeulich@novell.com>, Mark Kettenis <kettenis@gnu.org>
Cc: gdb-patches@sourceware.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH] x86 CFI extensions
Date: Sat, 17 Sep 2005 20:59:00 -0000 [thread overview]
Message-ID: <20050917205939.GD8777@nevyn.them.org> (raw)
In-Reply-To: <432717DB.76F0.0078.0@novell.com>
On Tue, Sep 13, 2005 at 06:18:03PM +0200, Jan Beulich wrote:
> >>> Richard Henderson <rth@twiddle.net> 12.09.05 09:49:14 >>>
> >On Mon, Sep 12, 2005 at 09:04:12AM +0200, Jan Beulich wrote:
> >> But truly I think the processor-specific pieces of Dwarf's
> >> frame unwind spec should provide numbering for the complete set of
> >> registers.
> >
> >Except there is no standards body for this. So *someone* will
> >have to make it up.
> >
> >Make it up and put it in gas and gdb: that will make it a defacto
> standard.
>
> This adds to gdb a little more than the minimum set of registers
> needed
> to at least fully understand CFI annotations for Linux' pt_regs.
>
> Built and tested on i686-pc-linux-gnu and x86_64-unknown-linux-gnu.
>
> Jan
>
> gdb/
> 2005-09-13 Jan Beulich <jbeulich@novell.com>
>
> * amd64-tdep.h (AMD64_FCTRL_REGNUM, AMD64_FSTAT_REGNUM,
> AMD64_MXCSR_REGNUM): New.
> * amd64-tdep.c (amd64_dwarf_regmap): Add eflags, selector regs,
> mxcsr, fp control and status words.
> * i386-tdep.c (): Add selector regs, mxcsr, fp control and
> status
> words.
Mark, did you want to take a look at this? It seems fine to me.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-09-17 20:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <432070850200007800024465@emea1-mh.id2.novell.com>
[not found] ` <20050908154645.GN3966@smtp.west.cox.net>
[not found] ` <43207BA30200007800024502@emea1-mh.id2.novell.com>
[not found] ` <20050908161334.GP3966@smtp.west.cox.net>
[not found] ` <43214D2D02000078000247B5@emea1-mh.id2.novell.com>
[not found] ` <20050910055836.GA28662@twiddle.net>
[not found] ` <4325448C0200007800024DF5@emea1-mh.id2.novell.com>
[not found] ` <20050912074914.GA31047@twiddle.net>
2005-09-13 16:17 ` Jan Beulich
2005-09-17 20:59 ` Daniel Jacobowitz [this message]
2005-09-17 22:32 ` Mark Kettenis
2005-09-17 22:40 ` Daniel Jacobowitz
2005-09-19 7:26 ` Jan Beulich
2005-09-21 20:02 ` Mark Kettenis
2005-09-22 8:22 ` Richard Henderson
2005-09-22 12:48 ` Daniel Jacobowitz
2005-09-23 7:42 Jan Beulich
2005-09-23 8:03 ` Eli Zaretskii
2005-09-23 12:57 ` Daniel Jacobowitz
2005-09-26 1:24 ` Daniel Jacobowitz
2005-09-26 7:04 ` Jan Beulich
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=20050917205939.GD8777@nevyn.them.org \
--to=drow@false.org \
--cc=JBeulich@novell.com \
--cc=gdb-patches@sourceware.org \
--cc=kettenis@gnu.org \
--cc=rth@twiddle.net \
/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