On Tue, Aug 25, 2015 at 1:53 PM, Gisle Vanem <gva...@yahoo.no> wrote: > Alexandre Pereira Nunes wrote: > >> See tdm-gcc, it works like that. > > I know (that's why I love TDM-gcc). But according to my: > f:\MingW32\MingW-w64\bin\gcc.exe -v --help > > MingW-w64 could do that too: > -m32 Generate 32bit i386 code > -m64 Generate 64bit x86-64 code > > 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. > > -- > --gv > > ------------------------------------------------------------------------------ > _______________________________________________ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public ------------------------------------------------------------------------------ _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
