This adds ExceptionHandling::MSVC, used by the x86_64-pc-windows-msvc
triple. It assumes that filter functions have already been outlined in
either the frontend or the backend. Filter functions are used in place
of the landingpad catch clause type info operands. In catch clause
order, the first filter to return true will catch the exception.
The C specific handler table expects the landing pad to be split into
one block per handler, but LLVM IR uses a single landing pad for all
possible unwind actions. This patch papers over the mismatch by
synthesizing single instruction BBs for every catch clause to fill in
the EH selector that the landing pad block expects.
Missing functionality:
- Accessing data in the parent frame from outlined filters
- Cleanups (from __finally) are unsupported, as they will require outlining and parent frame access
- Filter clauses are unsupported, as there's no clear analogue in SEH
In other words, this is the minimal set of changes needed to write IR to
catch arbitrary exceptions and resume normal execution.
Let's not call this just "MSVC" when we know that MSVC actually uses several different schemes.