Re: [Gems-users] Address assertion error on GEMS LogTM

[BYONG WU CHONG <bernard.chong@xxxxxxxx>]

Thank you, Dan.

 

I thought setting g_MEMORY_SIZE_BYTES to 2GB would solve the problem, but it didn’t. The error didn’t change.

 

However, I got GEMS’ EE/LL TM working with $GEMS/benchmarks/transactional/prioqueue benchmark.

This hints me that the problem might be on the SPLASH2 benchmark compilation.

 

I am not completely sure whether prioqueue worked perfectly, but this is the stat file I got from the simulation.

Could any of you read this stat file if this is good?

http://www.cs.utah.edu/~bchong/CA/debugging/GEMS-Micro_prioqueue_EETM_04.stats

http://www.cs.utah.edu/~bchong/CA/debugging/GEMS-Micro_prioqueue_LLTM_04.stats

 

Since prioqueue benchmark is working, there is a high chance that my SPLASH2 benchmark compilation is wrong.

Could any of you check if this SPLASH2 barnes benchmark is OK? I've compactly extracted only barnes part.

http://www.cs.utah.edu/~bchong/CA/debugging/SPLASH2_barnes.tbz2

For direct access

http://www.cs.utah.edu/~bchong/CA/debugging/SPLASH2_small/

Or if any of you have one working SPLASH2 benchmark on GEMS TM, please send me a copy.

 

BTW, I am using PROTOCOL=CMP_filter_directory for ruby compilation, do you think this is correct? I thought normal EE/LL TM would need same ruby protocol as ATMTP’s.

 

 

From: gems-users-bounces@xxxxxxxxxxx [mailto:gems-users-bounces@xxxxxxxxxxx] On Behalf Of Dan Gibson
Sent: Sunday, March 29, 2009 7:54 AM
To: Gems Users
Subject: Re: [Gems-users] Address assertion error on GEMS LogTM

 

Based on the contents of the memory map, set g_MEMORY_SIZE_BYTES to 2147483648.

Regards,
Dan

On Sun, Mar 29, 2009 at 12:35 AM, BYONG WU CHONG <bernard.chong@xxxxxxxx> wrote:

Hi,

I am having this assertion error while I am running SPLASH2 barnes on GEMS EE TM (LogTM).
-------------------- CLI ERROR LOG START --------------------
memoryBits: 3 memorySizeBits: 32 Address: [0x8796d1040, line 0x8796d1040]error: limit exceeded.  dataBlockBits: 6 memoryModuleBlocks: 8388608 index: 71087752 failed assertion 'index < RubyConfig::memoryModuleBlocks()' at fn integer_t Address::memoryModuleIndex() const in common/Address.h:210 failed assertion 'index < RubyConfig::memoryModuleBlocks()' at fn integer_t Address::memoryModuleIndex() const in common/Address.h:210 At this point you might want to attach a debug to the running and get to the crash site; otherwise press enter to continue
PID: 8176
-------------------- CLI ERROR LOG END --------------------

I did some research on this error and there was a thread that I should modify memory space so that I can avoid this error.
https://lists.cs.wisc.edu/archive/gems-users/2009-March/msg00059.shtml

My g_MEMORY_SIZE_BYTES is 4294967296 = 0x100000000

The output from "phys_mem0.map" is
simics> phys_mem.map
base               object               fn offs               length
0x0000000000000000 memory                0 0x0                0x80000000
0x0000000800000000 memory                0 0x80000000         0x80000000
0x000007fff07ffff0 simicsfs              0 0x0                0x10

Could someone tell me how should I avoid this assertion error?


The simics script is this
http://www.cs.utah.edu/~bchong/CA/debugging/barnes-EE-04-debug.simics

The LL TM python script used on above script is this
http://www.cs.utah.edu/~bchong/CA/debugging/tm_ee.py

The CLI output which contains the assertion error is this
http://www.cs.utah.edu/~bchong/CA/debugging/barnes-EE-04-debug-CLIout.txt

The console window output is this
http://www.cs.utah.edu/~bchong/CA/debugging/SPLASH2_barnes_EETM_04_debug.out

_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.

--
http://www.cs.wisc.edu/~gibson [esc]:wq!