It is now official, the cause of the mysterious gcc 3.3.5 exception
authorEric Andersen <andersen@codepoet.org>
Sun, 1 May 2005 00:34:11 +0000 (00:34 -0000)
committerEric Andersen <andersen@codepoet.org>
Sun, 1 May 2005 00:34:11 +0000 (00:34 -0000)
commit172f4c76b3476f95e9ae1478da97d245acf7b0b0
tree705eb1a91ca42f8cbe033d2666b53169dda81dc6
parent51b8148162a9b02837a83202b740612e702494d4
It is now official, the cause of the mysterious gcc 3.3.5 exception
handling failure is definately sjlj. Only enable it for the apparently
broken gcc 3.3.3 toolchain, which _does_ need it for exception handling
to work properly.
toolchain/gcc/Config.in