C++ Exceptions: Under the Hood (2013)
monkeywritescode.blogspot.com
C++ Exceptions: Under the Hood (2013)
1–10 of 116 posts
Re: C++ Exceptions: Under the Hood (2013)
#2[2013]ish if I remember.
Also note the ABI for C++ exceptions followed by G++ et al is actually documented as part of the Itanium C++ ABI :
Re: C++ Exceptions: Under the Hood (2013)
#3Under the hood of GCC specifically.
Re: C++ Exceptions: Under the Hood (2013)
#4Under the hood of GCC specifically.
Doesn't GCC support multiple exception handling options?
Re: C++ Exceptions: Under the Hood (2013)
#5[2013]ish if I remember. Also note the ABI for C++ exceptions followed by G++ et al is actually documented as part of the Itanium C++ ABI : https://itanium-cxx-abi.github.io/cxx-abi/abi-eh.html
The doc is actually incomplete, it refers to implementation defined ABI entry points for the actual unwinding. The actual unwind tables and compensation opcodes are, IIRC, part of the DWARF standard, but last time I looked at it that standard was also incomplete and left a lot unspecified. Many of the details (including bugs that have now become part of the ABI) are basically folklore.
IIRC Ian LAnce Taylor had a series of blog posts that did shed light on a lot of these details.
Re: C++ Exceptions: Under the Hood (2013)
#6Re: C++ Exceptions: Under the Hood (2013)
#7Re: C++ Exceptions: Under the Hood (2013)
#8Earlier quoted context omitted.
Doesn't GCC support multiple exception handling options?
I'm not sure what your point is - mine was that the original post is specifically about GCC, not Standard C++.
Mainly that exception handling doesn't have a single solution, even in GCC. I'm agreeing with you that this article only highlights one version of exception handling for one compiler.
There's also potential operating system involvement that's not really covered in this article.
Re: C++ Exceptions: Under the Hood (2013)
#9Under the hood of GCC specifically.
That's the article I used when I implemented exceptions in an LLVM-based compiler, so it's applicable to more than just GCC.