bugfix in ld/st algorithm and new measurements

This commit is contained in:
Jan Laukemann
2018-08-03 02:14:11 +02:00
parent 13cfb6bf5f
commit da5a27efd3
2 changed files with 3 additions and 1 deletions

View File

@@ -90,3 +90,5 @@ vsubpd-ymm_ymm_mem,1.0,3.0,"(0, 0, 1.0, 1.0, 0, 0, 0, 0, 1.0, 1.0)"
vsubsd-xmm_xmm_mem,0.5,3.0,"(0, 0, 0.5, 0.5, 0, 0, 0, 0, 0.5, 0.5)"
vsubsd-xmm_xmm_xmm,0.5,3.0,"(0, 0, 0.5, 0.5, 0, 0, 0, 0, 0, 0)"
vsubss-xmm_xmm_xmm,0.5,3.0,"(0, 0, 0.5, 0.5, 0, 0, 0, 0, 0, 0)"
vmovaps-xmm_mem,0.5,3.0,"(0.5, 0.5, 0, 0, 0, 0, 0, 0, 0.5, 0.5)"
movq_r64_xmm,1.0,-1,"(0, 0, 1.0, 0, 0, 0, 0, 0, 0, 0)"
Can't render this file because it contains an unexpected character in line 82 and column 41.

View File

@@ -58,7 +58,7 @@ class Scheduler(object):
# Count the number of store instr if we schedule for an architecture with par ld/st
if(self.en_par_ldst):
for i, instrForm in enumerate(self.instrList):
if(isinstance(instrForm[1], MemAddr)):
if(isinstance(instrForm[1], MemAddr) and len(instrForm) > 3):
print('({}) is st --> par_ldst = {}'.format(i, par_ldst + 1))
par_ldst += 1
# Check if there's a port occupation stored in the CSV, otherwise leave the