Cary Coutant wrote:
>> With SEH you can catch that kind of errors and that's why it's so
>> interesting in embedded world
>
> That's also why SEH is a major pain for optimization. The compiler
> would have to identify every instruction that may trigger an
> exception,
Isn't that what the "__try" block scope is there to tell you? Or are you
considering if it were to be done automatically?
> On top of that, the filters can return a code that tells the EH
> mechanism to resume execution at the original exception point as if
> nothing happened. Just trying to understand all the implications of
> that makes my head hurt.
For background reading, the Matt Pietrek win32 SEH article would be the
canonical source. (Don't have the URL to hand but those words should google
it straight up for you).
Really, it's all pretty much the same as DW2, except that rather than
calling a raise exception function in libgcc, it begins with a real processor
exception that then ends up routing into the unwinder. From there it's all
fairly analagous.
cheers,
DaveK
