From: "Jan Beulich" <JBeulich@novell.com>
To: <drow@false.org>,"Mark Kettenis" <mark.kettenis@xs4all.nl>
Cc: <gdb-patches@sourceware.org>,<rth@twiddle.net>
Subject: Re: [PATCH] x86 CFI extensions
Date: Mon, 19 Sep 2005 07:26:00 -0000 [thread overview]
Message-ID: <432E8493.76F0.0078.0@novell.com> (raw)
In-Reply-To: <200509172231.j8HMVimO002293@elgar.sibelius.xs4all.nl>
>>> Mark Kettenis <mark.kettenis@xs4all.nl> 18.09.05 00:31:44 >>>
>> Date: Sat, 17 Sep 2005 16:59:39 -0400
>> From: Daniel Jacobowitz <drow@false.org>
>>
>> > 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.
>
>Sorry, slipped through. Thanks for reminding me Daniel!
>
>Jan, what's the status new DWARF register numbers? At least the
amd64
>ones look very Linux-specific to me. They're not listed in the AMD64
>ABI (at least not version 0.95), and AFAICT gcc won't produce them
>either.
In addition to Daniel's reply: while gcc will probably never care about
them (and thus never produce them), the gas now can (patch went in last
week), and while initially this indeed is for Linux, any OS should want
them for describing exception and interrupt frames...
Jan
next prev parent reply other threads:[~2005-09-19 7:26 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
2005-09-17 22:32 ` Mark Kettenis
2005-09-17 22:40 ` Daniel Jacobowitz
2005-09-19 7:26 ` Jan Beulich [this message]
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=432E8493.76F0.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--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