| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Register reads/writes done in startup() count against the stats while they
don't count if done in initState().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Exclude bzip2 for now. It works, it just takes too long to run.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Coherence protocol change basically got rid
of UpgradeReqs in L2 caches, other minor
related cache stat changes.
|
|
Because the handling of the E state for multilevel caches
has changed, stats are affected for any non-ruby config
with caches, even uniprocessor simple CPU.
|
|
|
|
Rename 'responder_set' to 'use_default_range'.
|
|
|
|
|
|
|
|
|
|
|
|
Caused by a slight change in memory layout.
|
|
|
|
they're easier to diff
|
|
Because of the initialization bug, it wasn't consistent anyway.
|
|
Mostly just config.ini updates, though the different response
latency for bad addresses caused very minor timing changes
in the O3 Linux boot tests.
|
|
|
