> 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, and either treat that instruction as a scheduling boundary or create a new landing pad for the instruction (where compensation code can be placed to adjust for the effects of instructions moved up or down). The former inhibits a lot of optimization, while the latter blows up the size of the EH tables and the corresponding landing pad code. 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. -cary
