Hello
1. I am able to successfully generate the executable gem5 simulator for [ARM ISA, MESI_Three_Level protocol]. The command I used being: a. scons -j4 build/ARM_MESI_3_level/gem5.opt --default=ARM PROTOCOL=MESI_Three_Level SLICC_HTML=True 2. Also, I am able successfully generate the executable gem5 simulator for [X86 ISA, MESI_Three_Level protocol]. The command I used being: a. scons -j4 build/X86_MESI_3_level/gem5.opt --default=X86 PROTOCOL=MESI_Three_Level SLICC_HTML=True However, if I look in src/mem/ruby/protocol, the code for MESI_Three_Level is as follows: [j00533938@lhrplinux00001 protocol]$ ll MESI_Three_Level* -rw-rw-r-- 1 j00533938 j00533938 40031 May 28 09:17 MESI_Three_Level-L0cache.sm -rw-rw-r-- 1 j00533938 j00533938 36841 May 28 09:17 MESI_Three_Level-L1cache.sm -rw-rw-r-- 1 j00533938 j00533938 4270 May 28 09:17 MESI_Three_Level-msg.sm -rw-rw-r-- 1 j00533938 j00533938 316 Mar 20 17:42 MESI_Three_Level.slicc Therefore, it looks to me that the code for MESI_Three_Level is not complete. Thus it is not clear to me how the executable gem5 simulator for MESI_Three_Level is being generated. Any thoughts on this please? Thanks in advance. JO
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
