On Tue, Aug 25, 2015 at 9:59 AM, Ray Donnelly <mingw.andr...@gmail.com>
wrote:
> On Tue, Aug 25, 2015 at 1:53 PM, Gisle Vanem <gva...@yahoo.no> wrote:
> > I was under the impression that:
> > f:\MingW32\MingW-w64\bin\gcc.exe
> >
> > was just a driver for the right <prefix>gcc.exe.
> > True or false?
>
> False. Back when Apple used GCC they had such a wrapper to two
> distinct GCC builds.
>
> There's a good reason not to use -m32 and -m64. You want to use SEH
> for Win64 since it's fastest but you can only use sjlj or dwarf2
> exceptions for Win32. Making a 'multilib' MinGW-w64 GCC forces the
> same exception model on both.
>
>
the 64-bit tdm-gcc has SEH with -m64 and sjlj with -m32 on the same
multilib toolchain. Perhaps it patches gcc/binutils/whatever, but it should
be trivial to port the behavior to a custom build.
------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
