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) Thanks. Yuanhui Zhang ------------------------------------------------------------------------------ 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
