public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: George Kraft IV <gk4@austin.ibm.com>
To: lsb-spec@freestandards.org
Cc: lsb-confcall@lists.sourceforge.net, mark@codesourcery.com,
	oldham@codesourcery.com, gcc@gcc.gnu.org
Subject: Standardizing _Unwind_* error handling interfaces found in libgcc_s.so
Date: Thu, 10 Oct 2002 10:30:00 -0000	[thread overview]
Message-ID: <1034264848.1139.46.camel@gkraft4.austin.ibm.com> (raw)

The following _Unwind C++ error handling interfaces found in libgcc_s.so
are being added to the LSB's ABI for v1.3.  Please review, then submit
your comments.

http://www.linuxbase.org/spec/wip/wip/libgcc-sman.html

(give the above link until Friday 10/11/02 to refresh)

https://sourceforge.net/tracker/?func=add&group_id=1107&atid=101107

_Unwind_DeleteException -- private C++ error handling method
_Unwind_Find_FDE -- private C++ error handling method
_Unwind_GetGR -- private C++ error handling method
_Unwind_GetIP -- private C++ error handling method
_Unwind_GetLanguageSpecificData -- private C++ error handling method
_Unwind_GetRegionStart -- private C++ error handling method
_Unwind_RaiseException -- private C++ error handling method
_Unwind_Resume -- private C++ error handling method
_Unwind_SetGR -- private C++ error handling method
_Unwind_SetIP -- private C++ error handling method

_Unwind_GetDataRelBase -- private IA64 C++ error handling method
_Unwind_GetTextRelBase -- private IA64 C++ error handling method

Also, if anyone has any tests cases they could offer, then that would be
great.

Thanks,

George (gk4)



             reply	other threads:[~2002-10-10 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 10:30 George Kraft IV [this message]
2002-10-10 12:05 ` Richard Henderson
2002-10-10 12:15   ` [lsb-spec] " 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=1034264848.1139.46.camel@gkraft4.austin.ibm.com \
    --to=gk4@austin.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=lsb-confcall@lists.sourceforge.net \
    --cc=lsb-spec@freestandards.org \
    --cc=mark@codesourcery.com \
    --cc=oldham@codesourcery.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).