-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03.10.2013 11:06, asmwarrior wrote: > On 2013-10-3 12:27, LRN wrote: >> Always use --build=i686-w64-mingw32 or --build=x86_64-w64-mingw32 when >> using mingw-w64 toolchains (obviously, for cross-toolchains you would >> use --host=i686-w64-mingw32 and --host=x86_64-w64-mingw32). >> - --build=mingw32 only works for mingw.org toolchains. >> >> [arch]-w64-mingw32 has other benefits too (at least at this moment; see >> the config.guess thread). > Thanks for your explanation. I have just opened the config.log to see what is > the benefits. But I can't see much. > > Here is the result of my build case: > configure:3962: checking build system type > configure:3976: result: i386-pc-mingw32 > configure:3996: checking host system type > configure:4009: result: i386-pc-mingw32 > configure:4029: checking target system type > configure:4042: result: i386-pc-mingw32 > > Do you mean that i686-w64-mingw32 will have better optimization code > generated? (code instruction for i686, not i386)
I meant mostly the "w64" part. CPU arch is a different matter; that said, some packages (like glib) require i686 at the least, so i386 stops being an option (for me at least). As for "w64", the details are a bit sketchy (as i have not read the relevant parts of the. What i know for sure is that if `gcc -dumpmachine` doesn't say "w64", then certain features won't work (such as -municode flag). Vendor key is set when the toolchain is built, and, presumably, you may have both, say, i686-pc-mingw32-gcc.exe and i686-w64-mingw32-gcc.exe, so later, when you use the tooclahin, specifying the right build/host will ensure that the right toolchain is used (config.guess tends to guess i*86-pc-mingw32). If your gcc is just "gcc.exe", and you don't have i*86-pc-mingw32-*, then maybe (just maybe) not specifying build/host will not do any harm. Still, build/host values may be used for more things than just selecting a toolchain, so i wouldn't risk it. I'm not sure if your choice of vendor key affects gcc _after_ gcc is compiled. - -- O< ascii ribbon - stop html email! - www.asciiribbon.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQEcBAEBAgAGBQJSTS85AAoJEOs4Jb6SI2CwrSIH/i2MbkFU6owLcGZqxFu0GflE CfHHeU09GF2zjB2GvG9LqX/5LQqrfgFbHyGxhNN9oZH9Px6SoYJfwZi2Oe6q1L4F z+rM+DS+zoB00tHTJUR2f1BzJ7OM5cz6ALNXYE6F8BQVe166UXeyfTB7SjWaWIzX mZ1QA8D1Ll9uF2LSIeyU8OGmvCHNLB748vTpzEtzNg4GUYNWYSKMaw44Sg9iLWzq 0iuvmtMwz9zSYb54vkF/BMY6P0RlgwhMxe6BNunHz226CVETYYo6utid3lE54R+q LroudkHj57Znv+IeSxakMaLuZUoTIWswchY2JaOajUiJ54WStoAiNDK4yVJMJmg= =P70+ -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
