remove-unreachable-traps

[Ondrej LHOTAK <olhotak@sable.mcgill.ca>]

I was wondering whether anyone knows why the remove-unreachable-traps
option defaults to false in the UnreachableCodeEliminator. In fact, I
wonder why it's even an option to not remove. If unreachable traps are
left in, it is not possible to produce bytecode from baf: these traps
have no entry points, so the baf code assumes their initial stack height
is zero, yet the first thing they do is pop the exception. Does anyone
remember why they are not removed by default?

Ondrej