Author: Fabien Letouzey
Date: 23:39:09 03/28/05
Go up one level in this thread
On March 28, 2005 at 11:36:10, Dieter Buerssner wrote: >On March 28, 2005 at 02:34:43, Fabien Letouzey wrote: > >>Yes, I can see from your log file that output starts going crazy right after a >>64-bit number is displayed (node #). That's > >I don't know any context here, and have no idea what compiler is beeing used. >Perhaps the following info can still be useful. I believe the MinGW compiler >environment will not support the Standard C format specifiers for [unsigned] >long long, but instead will support the MSVC type specifiers (%I64u). It may >give a warning (and no warning with the not working %llu). Intel compiler on >Windows and MSVC (and probably Borland compilers, too) will not support %llu. >The easiest thing to do might be to use %.0f and a cast of the argument to >double. It should print all numbers up to 2^53 correctly up to the last digit. > >Regards, >Dieter Thanks Dieter! That must be it. I was coming to the conclusion of not-working format string as well (thanks to the log report earlier in this thread). Before yesterday I thought all arguments were bogus ... However I always forget that (new to me) MinGW compiler that claims to be GCC on Windows. Many things that work with Cygnus GCC don't with MinGW it seems (MinGW cannot compile PolyGlot for instance). I already use a conditional definition for 64-bit integer display. What's needed is to add MinGW to the list of compilers that require %I64u. What is the compiler "define" for (all versions of) MinGW? BTW, why would a GCC-claim-to-be compiler use M$ convention??? Fabien.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.