From: Richard Henderson <rth@twiddle.net>
To: Jan Beulich <JBeulich@novell.com>
Cc: Tom Rini <trini@kernel.crashing.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 CFI annotations
Date: Mon, 12 Sep 2005 00:49:14 -0700 [thread overview]
Message-ID: <20050912074914.GA31047@twiddle.net> (raw)
In-Reply-To: <4325448C0200007800024DF5@emea1-mh.id2.novell.com>
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.
r~
next prev parent reply other threads:[~2005-09-12 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 15:10 [PATCH] i386 CFI annotations Jan Beulich
2005-09-08 15:46 ` Tom Rini
[not found] ` <43207BA30200007800024502@emea1-mh.id2.novell.com>
[not found] ` <20050908161334.GP3966@smtp.west.cox.net>
2005-09-09 6:51 ` Jan Beulich
2005-09-10 5:58 ` Richard Henderson
2005-09-12 7:04 ` Jan Beulich
2005-09-12 7:49 ` Richard Henderson [this message]
2005-09-12 13:09 ` Daniel Jacobowitz
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=20050912074914.GA31047@twiddle.net \
--to=rth@twiddle.net \
--cc=JBeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.org \
/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