summaryrefslogtreecommitdiff
path: root/toolchain/gcc/Config.in
diff options
context:
space:
mode:
authorEric Andersen <andersen@codepoet.org>2005-05-01 00:34:11 +0000
committerEric Andersen <andersen@codepoet.org>2005-05-01 00:34:11 +0000
commit172f4c76b3476f95e9ae1478da97d245acf7b0b0 (patch)
tree705eb1a91ca42f8cbe033d2666b53169dda81dc6 /toolchain/gcc/Config.in
parent51b8148162a9b02837a83202b740612e702494d4 (diff)
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.
Diffstat (limited to 'toolchain/gcc/Config.in')
-rw-r--r--toolchain/gcc/Config.in3
1 files changed, 2 insertions, 1 deletions
diff --git a/toolchain/gcc/Config.in b/toolchain/gcc/Config.in
index ce0a5ab50..b19a36dec 100644
--- a/toolchain/gcc/Config.in
+++ b/toolchain/gcc/Config.in
@@ -59,7 +59,8 @@ config BR2_GCC_VERSION
config BR2_GCC_USE_SJLJ_EXCEPTIONS
string
- default "--enable-sjlj-exceptions"
+ default "--enable-sjlj-exceptions" if BR2_GCC_VERSION_3_3_3
+ default ""
help
Currently the unwind stuff seems to work for staticly linked apps
but not dynamic. So use setjmp/longjmp exceptions by default.