Related articles |
---|
Typical C++ Exception Handling implementations drahardja@gmail.com (Dave Rahardja) (2005-10-03) |
Re: Typical C++ Exception Handling implementations Ranjit.Mathew@oracle.com (Ranjit Mathew) (2005-10-04) |
Re: Typical C++ Exception Handling implementations haberg@math.su.se (2005-10-06) |
From: | "Dave Rahardja" <drahardja@gmail.com> |
Newsgroups: | comp.compilers |
Date: | 3 Oct 2005 00:30:38 -0400 |
Organization: | http://groups.google.com |
Keywords: | C++, errors, question |
Posted-Date: | 03 Oct 2005 00:30:38 EDT |
Can someone share some ways that current compilers deal with the C++
exception handling mechanism? I'm especially curious about the
overheads associated with the various techniques.
In particular, I'd like to know:
- Ways to track which automatic objects have been constructed and need
to be destructed, and in which order
- If static-analysis methods exist, and what the relative overheads are
of such techniques versus run-time stack-bound methods
- Where the exception object is stored, and when it is constructed and
destructed
- Ways to match the exception object type against the catch handlers
-dr
Return to the
comp.compilers page.
Search the
comp.compilers archives again.