From bd7ed099dc120ca602006eb18705f7caa394e36d Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Mon, 18 Jul 2005 23:34:20 +0000 Subject: Apply the fix for gcc bug #22167 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22167 remove gcc 3.3.3, change config for sjlj exception handling a bit. --- toolchain/gcc/Config.in | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) (limited to 'toolchain/gcc/Config.in') diff --git a/toolchain/gcc/Config.in b/toolchain/gcc/Config.in index 2ecd965f3..912e4b4c8 100644 --- a/toolchain/gcc/Config.in +++ b/toolchain/gcc/Config.in @@ -8,9 +8,6 @@ choice help Select the version of gcc you wish to use. - config BR2_GCC_VERSION_3_3_3 - bool "gcc 3.3.3" - config BR2_GCC_VERSION_3_3_5 bool "gcc 3.3.5" @@ -39,7 +36,6 @@ endchoice config BR2_GCC_VERSION string - default "3.3.3" if BR2_GCC_VERSION_3_3_3 default "3.3.5" if BR2_GCC_VERSION_3_3_5 default "3.3.6" if BR2_GCC_VERSION_3_3_6 default "3.4.2" if BR2_GCC_VERSION_3_4_2 @@ -51,12 +47,13 @@ config BR2_GCC_VERSION config BR2_GCC_USE_SJLJ_EXCEPTIONS - string - default "--enable-sjlj-exceptions" if BR2_GCC_VERSION_3_3_3 - default "" + bool "Enable setjmp/longjmp exceptions?" + default n help - Currently the unwind stuff seems to work for staticly linked apps - but not dynamic. So use setjmp/longjmp exceptions by default. + For some platforms, proper stack unwinding works perfectly, + while other platforms must use setjmp/longjmp exceptions for + proper stack unwinding during exception handling. Most people + can leave this set to n. config BR2_EXTRA_GCC_CONFIG_OPTIONS string "Additional gcc options" -- cgit v1.2.3