Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread Алексей Павлов
Ok I try it now. 2012/11/22 Kai Tietz : > 2012/11/22 niXman : >> 2012/11/22 Kai Tietz: >>> Well, __SEH__ is defined for x64 in any case. There is no way to have >>> for x64 no SEH-support - at least not in a way it would work in a >>> general way, as SEH is part of the ABI of x64. >> I.e. SJLJ ca

Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread Kai Tietz
2012/11/22 niXman : > 2012/11/22 Kai Tietz: >> Well, __SEH__ is defined for x64 in any case. There is no way to have >> for x64 no SEH-support - at least not in a way it would work in a >> general way, as SEH is part of the ABI of x64. > I.e. SJLJ can't be used for 4.8(and later)-x86_64? > >> I am

Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread Алексей Павлов
With 64bit multilib toolchain is the same situation as with 32bit multilib toolchain

Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread niXman
2012/11/22 Kai Tietz: > Well, __SEH__ is defined for x64 in any case. There is no way to have > for x64 no SEH-support - at least not in a way it would work in a > general way, as SEH is part of the ABI of x64. I.e. SJLJ can't be used for 4.8(and later)-x86_64? > I am about to setup a build for t

Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread Kai Tietz
2012/11/22 niXman : > 2012/11/22 niXman: >> I once asked a similar question, but didn't understand, whether sjlj >> use will be available for 4.8? > > Because I a few months can not build trunk with sjlj successfully. > I wrote about this in the gcc-help mailing list, I think twice. Well, __SEH__

Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread niXman
2012/11/22 niXman: > I once asked a similar question, but didn't understand, whether sjlj > use will be available for 4.8? Because I a few months can not build trunk with sjlj successfully. I wrote about this in the gcc-help mailing list, I think twice. -- Regards, niXman __

Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread niXman
2012/11/22 Kai Tietz: > Hi, > > the cause for this is that SEH exceptions are only present for x64 > 64-bit target. There is no such support for 32-bit (mainly caused by > patent issues). Therefore if you want to build multilib for mingw, > then please switch back to SjLj-exception mechanism. I

Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread Алексей Павлов
My configure line is: $ /temp/mingw-sources/gcc-trunk/gcc/configure --cache-file=./config.cache --prefix=/temp/x32-trunk-snapshot-posix-sjlj-rev1/prefix --with-sysroot=/temp/x32-trunk-snapshot-posix-sjlj-rev1/prefix --enable-shared --enable-static --enable-targets=all --enable-multilib --enable-li

Re: Always defined __SEH__ when build from trunk

2012-11-22 Thread Kai Tietz
Hi, the cause for this is that SEH exceptions are only present for x64 64-bit target. There is no such support for 32-bit (mainly caused by patent issues). Therefore if you want to build multilib for mingw, then please switch back to SjLj-exception mechanism. Regards, Kai

Always defined __SEH__ when build from trunk

2012-11-22 Thread Алексей Павлов
Hi! When I try to build gcc from trunk with mingw-w64 I successfully build only 64bit with seh exceptions. Other builds stop on error ../../../../../../mingw-sources/gcc-trunk/libgcc/unwind-c.c:238:1: warning: no previous prototype for '__gcc_personality_seh0' [-Wmissing-prototypes] __gcc_person