2012/8/8 Ruben Van Boxem: > That's not what was implemented. What was implemented is the > native (MSVC compatible?) Win64 native exception handling. Why Win64? SEH that, only for Win64 is implemented/works?
P.S. Probably my questions seem silly, but I never worked for windows. Some years I work as the programmer for Linux, and never thought about on how are implemented an exceptions and how many implementations exist =) > It is something like the dw2/sjlj eh, but better: it allows MSVC-code > originating exceptions to be thrown over GCC generated code and I would > guess vice versa. sjlj does this as well, but this seh does it without > performance penalty. What it is more preferable to development for windows? Whether it is possible to argue, what SEH always the most preferred choice? > I have, and Jon_y has built a multilib compiler. It is necessary to build in some stages? 1) all-target-libgcc 2) all-gcc 3) all I am right? P.P.S. Please, delete my e-mail when answering ;) Thanks. -- Regards, niXman ___________________________________________________ Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows: http://sourceforge.net/projects/mingwbuilds/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
