From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Lockups on 2.4.1
Date: Mon, 26 Feb 2001 20:52:41 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005207@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005175@msgid-missing>
>2. What is this new unwind stuff?
You probably want to know in the context of the kernel. I can't answer that.
I can answer in the context of C++. The unwind stuff is used for exception
handling. When a program throws, we use the unwind stuff to unwind stack
frames back to where the exception handler (catch clause) is. The unwind
data is similar in spirit to the DWARF2 frame info that is currently used by
most all other gcc targets. It is basically the same data just encoded
differently.
The format of the data is documented in the Software Conventions and Runtime
Architecture manual, section 11. The library interface for C++ EH is
documented in the psABI, section 6. This hasn't been implemented yet, we are
working on it right now.
Jim
next prev parent reply other threads:[~2001-02-26 20:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 16:05 [Linux-ia64] Re: Lockups on 2.4.1 Bill Nottingham
2001-02-21 17:16 ` Gerrit Huizenga
2001-02-21 17:57 ` David Mosberger
2001-02-21 18:58 ` Chris McDermott
2001-02-21 21:02 ` David Mosberger
2001-02-23 15:19 ` Jun Nakajima
2001-02-23 19:06 ` Seth, Rohit
2001-02-23 19:20 ` Michael Madore
2001-02-23 19:48 ` Seth, Rohit
2001-02-23 20:00 ` Jesse Barnes
2001-02-24 13:39 ` Francis Galiegue
2001-02-24 14:44 ` Francis Galiegue
2001-02-24 18:45 ` Michael Madore
2001-02-24 23:18 ` Joseph V Moss
2001-02-25 2:43 ` Francis Galiegue
2001-02-26 20:52 ` Jim Wilson [this message]
2001-03-07 3:51 ` [linux-ia64] " Tom King
2001-03-07 20:34 ` Jim Wilson
2001-03-08 3:45 ` Tom King
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=marc-linux-ia64-105590693005207@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.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