gem5/tests/quick/00.hello/ref/alpha/linux
Korey Sewell b5736ba4ef alpha:o3:simple: update simout/err files
A few prior changesets have changed the gem5 output in a way that wont cause
errors but may be confusing for someone trying to debug the regressions. Ones that I caught
were:
- no more "warn: <hash address"
- typo in the ALPHA Prefetch unimplemented warning

Additionaly, the last updated stats changes rearrange the ordering of the stats output even though
they are still correct stats (gem5 is smart enough to detect this). All the regressions pass
w/the same stats even though it looks like they are being changed.
2011-06-20 18:57:14 -04:00
..
inorder-timing inorder: update SE regressions 2011-06-19 21:43:42 -04:00
o3-timing alpha:o3:simple: update simout/err files 2011-06-20 18:57:14 -04:00
simple-atomic alpha:o3:simple: update simout/err files 2011-06-20 18:57:14 -04:00
simple-timing alpha:o3:simple: update simout/err files 2011-06-20 18:57:14 -04:00
simple-timing-ruby regress: updates after changing ruby network bandwidth 2011-04-28 17:18:16 -07:00
simple-timing-ruby-MESI_CMP_directory regress: updates after changing ruby network bandwidth 2011-04-28 17:18:16 -07:00
simple-timing-ruby-MOESI_CMP_directory regress: updates after changing ruby network bandwidth 2011-04-28 17:18:16 -07:00
simple-timing-ruby-MOESI_CMP_token regress: updates after changing ruby network bandwidth 2011-04-28 17:18:16 -07:00
simple-timing-ruby-MOESI_hammer regress: updates after changing ruby network bandwidth 2011-04-28 17:18:16 -07:00