On 3/22/2013 18:22, Ruben Van Boxem wrote: >>> >>> Yes, another compatibility issue. I've been using the dwarf2 version. >>> (But there are sjlj advocates out there.) >>> >> >> Yes, DW2 is quite frankly broken on Windows, since you'll never be able >> to recompile system libraries to be able to throw through it (or 3rd >> party code built with MSVC). It is even more broken on win64. >> > > I agree with you, but DW2 isn't broken: the use case of using MSVC-built > code with MinGW-w64 GCC is not common (it usually is the other way around), > but it is an (the only?) advantage of SJLJ for x86 Windows. On the other > hand, the performance penalty is real (I've been notified of this by > several users) and can be "solved" by using the dw2 implementation. >
I agree, sort of. Not too long ago we were pushed a patch to allow static linking with MSVC. The author claimed that mingw has always worked with MSVC static linking until recently. The patch was never accepted because it was way too intrusive that it broke the GCC side. > For Win64, GCC 4.8 brings the long-needed seh. I doubt anyone will be using > sjlj on win64 after that. > Sure, 32bit part will be ready when patent expires. > > PS: Win64, x64, x86_64, AMD64, blablabla ;-) > You forgot EMT64 vs x86_64 vs x86-64 vs IA32e :)
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
