From: zhou d. <dra...@gm...> - 2008-01-03 15:51:08
|
2008/1/3, Wesley W. Terpstra <we...@te...>: > On Jan 2, 2008, at 10:37 PM, NightStrike wrote: > >> I've also noticed some problems persist in the new build: > >> stdint.h defines bad values for [U]INTPTR_* ... it thinks its 32 bit > >> libmingwex.a renamed gettimeofday to mingw_gettimeofday Can you give some testcase code for this two problems ? I do some small test, but do not get any problem. > > > > I've never used any of drangon's builds, but you can try the ones that > > are on the sourceforge downloads page: > > https://sourceforge.net/project/showfiles.php?group_id=202880 > > I'd seen those. I only used drangon's build because it was newer. I try to compile a compile a new package once per one or two month, I think that mingw-w64 is still not too stable, and need more test. I will post my build script on the website some day later. You can try to cross build your toolchain form source code, If there is any problem in my build script, please point it out. The cross compiler is more stable than the native compiler, The cross compiler can always build the native compiler or other program. but the native sometimes failed. I don't know whether it is caused by the build script I used. The old native toolchain built in Sep 2007 seems better, later, it crashed when compiled with " -pipe " flag, and later, the g++.exe failed to build large source code. So, I recommend to use cross compiler to build native winx64 program. I try to use windbg to find where the native toolchain went wrong, but it's too difficult. Maybe I need to wait gdb to be ported. > > > You might want to wait a day or two, though. > > I can wait. Are the two issues I mentioned above addressed in it? I > have work-arounds, so no rush. > > > What is your host system? I'll try to do that one first. > > I can use either a mingw i386 or amd64 hosted compiler which outputs > amd64. > > I'd prefer an amd64->amd64 compiler, as that's the ultimate goal. > OTOH, I've had bad luck with the win64 native compilers. Are they more > reliable now? > > One final note: can anyone recommend a good reference on the win64 > calling convention? MLton can output amd64 assembler and I'll need to > fix this eventually. calling convention ? Do you means the following document ? http://www.x86-64.org/documentation/abi-0.99.pdf > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > |