Author: Hristo
Date: 08:57:21 10/24/99
Go up one level in this thread
On October 23, 1999 at 18:05:57, Michel Langeveld wrote:
>>>But after checking the code I can't find none if this. Can you be more specific
>>>and tell the line number of which the compiler warns...
>>
>>neither can I :((
>>For instance hash.c line 51, 64, 166, 179, 412, 447, 466, 481, 505, 521
>>all produce the above mentioned warning.
>
>Does Crafty 16.19 also puge such output?
>My version of hash.c of Crafty 16.10 hash to folowing properties:
>06/07/99 10:08a 12,438 HASH.C
>
>and is only 297 lines long?? Is this the version you use? Can you recheck the
>file and the numbers please... If you have a different version of hash.c then
>please mail it to me: rudolf@stad.dsl.nl
>
You are absolutely correct.
hash.c 12438 -> 297 lines in C
The errors seem to come from the assembler ...
then the line numbers are different, bizare.
I want to get the assemebly code going now ...
so we can check it out ...
hristo
>I checked line 51 and it's a comment line. Line 52 is the folowing:
>tree->hash_move[ply] = 0
>
>Can you put the assembly code of Cygnos to screen/file? I'm very curious what
>assembly output it generated.
>
>hash_move is declared in chess.h as
>struct tree
>{
> .....
> int hash_move[MAXPLY];
> ...
>};
>
>typedef struct tree TREE;
>
>So it might be that = 0 is seen as an 16 bit value and int hash_move is seen as
>32bit.
>
>Maybe you have to set or reset some compiling switches.
>
>Kind regards,
>
>Michel Langeveld
This page took 0.01 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.