GCC info

[demone]

I want some info about the new Code::blocks release:

wich GCC version are C::B using?

the one with SJLJ or Dwarf 2 unwindingi?

underlying GCC version.. is 4.7.1 or 4.7.0?

thx.

[Jenna]

C:\Program Files\CodeBlocks\MinGW\bin>gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=c:/program files/codeblocks/mingw/bin/../libexec/gcc/mingw32/4.7.1/lto-wrapper.exe
Target: mingw32
Configured with: ../../src/gcc-4.7.1/configure --build=mingw32
--enablelanguages=c,c++,ada,fortran,objc,obj-c++ --enable-threads=win32 --enable-libgomp
--enable-lto --enable-fully-dynamic-string --enable-libstdcxx-debug --enable-version-specific-runtime-libs
--with-gnu-ld --disable-nls --disable-win32-registry --disable-symvers
--disable-build-poststage1-with-cxx --disable-werror --prefix=/mingw32tdm
--with-local-prefix=/mingw32tdm --enable-cxx-flags='-fno-function-sections -fno-data-sections'
--with-pkgversion=tdm-1 --enable-sjlj-exceptions
--with-bugurl=http://tdm-gcc.tdragon.net/bugs
Thread model: win32
gcc version 4.7.1 (tdm-1)

[demone]

thanks! great to see sjlj . good job with this new IDE.

[thomas]

How is seeing sjlj great? It is the by far most inferior way of exception handling, on any architecture.

The only advantage of sjlj over dw2 (solely under Win32) is that it works with exceptions that take a weird way through system DLLs, which really isn't an advantage if you ask me (shouldn't happen in the first place). And in respect of vectored exception handling, it has no advantage at all.