[gem5-users] Error when running SPEC 2006 ***gobmk***

[梁政]

Hi

I am running the SPEC 2006 benchmark on gem5. When I run gobmk, the program itself prints following error messages and exits quickly:




"

? cannot open or parse 'golois/Goemate990902-15.sgf'

? 1 vertex must not be empty




? cannot open or parse 'golois/Goemate990902-15.sgf'







? 1 vertex must not be empty




...

"

It seems the problem comes from the gobmk benchmark itself. I think gem5 can run itcorrectly. Then I dug into the codes and found that these messages are print by 'gtp_failure'. It is a GNU library function. I used -static in the compilation. I can run the benchmark and have correct outputs on my physical machine. So what may happen when I port the program to the gem5 simulator? I think the sgf file format may have some portability issues. (I have tested it on both x86 and ALPHA architectures. Results are the same)




Best Regards

Zheng Liang

EECS, Peking University

[梁政]

Sorry for my mistake. I found my problem. I didn't run gem5 in the path where the binary file and input data locates


-----Original Messages-----
From:"梁政" <***@pku.edu.cn>
Sent Time:2018-11-21 06:08:06 (Wednesday)
To: gem5-***@gem5.org, ***@gnu.org
Cc:
Subject: [gem5-users] Error when running SPEC 2006 ***gobmk***



Hi

I am running the SPEC 2006 benchmark on gem5. When I run gobmk, the program itself prints following error messages and exits quickly:




"

? cannot open or parse 'golois/Goemate990902-15.sgf'

? 1 vertex must not be empty




? cannot open or parse 'golois/Goemate990902-15.sgf'







? 1 vertex must not be empty




...

"

It seems the problem comes from the gobmk benchmark itself. I think gem5 can run itcorrectly. Then I dug into the codes and found that these messages are print by 'gtp_failure'. It is a GNU library function. I used -static in the compilation. I can run the benchmark and have correct outputs on my physical machine. So what may happen when I port the program to the gem5 simulator? I think the sgf file format may have some portability issues. (I have tested it on both x86 and ALPHA architectures. Results are the same)




Best Regards

Zheng Liang

EECS, Peking University