From: "Wichmann, Mats D" <mats.d.wichmann@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>, Richard Henderson <rth@redhat.com>
Cc: George Kraft IV <gk4@austin.ibm.com>,
lsb-spec@freestandards.org, lsb-confcall@lists.sourceforge.net,
mark@codesourcery.com, oldham@codesourcery.com, gcc@gcc.gnu.org
Subject: RE: [lsb-spec] Re: Standardizing _Unwind_* error handling interfa ces found in libgcc_s.so
Date: Thu, 10 Oct 2002 12:51:00 -0000 [thread overview]
Message-ID: <39B5C4829263D411AA93009027AE9EBB1EF4521A@fmsmsx35.fm.intel.com> (raw)
=
> It's also not clear if they're CPU-specific. I know that
> some of these
> are actually in the psABI on x86-64.
Just two were listed as ia64 CPU-specific
(interestingly, those two don't appear in the ia64 psABI,
I'm still curious where they come from).
next reply other threads:[~2002-10-10 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 12:51 Wichmann, Mats D [this message]
2002-10-10 15:18 ` Jim Wilson
2002-10-10 20:25 ` Richard Henderson
2002-10-10 22:41 ` Jim Wilson
2002-10-11 1:05 ` H. Peter Anvin
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=39B5C4829263D411AA93009027AE9EBB1EF4521A@fmsmsx35.fm.intel.com \
--to=mats.d.wichmann@intel.com \
--cc=gcc@gcc.gnu.org \
--cc=gk4@austin.ibm.com \
--cc=hpa@zytor.com \
--cc=lsb-confcall@lists.sourceforge.net \
--cc=lsb-spec@freestandards.org \
--cc=mark@codesourcery.com \
--cc=oldham@codesourcery.com \
--cc=rth@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).