o3: fix tick used for renaming and issue with range selection
authorMatt Horsnell <Matt.Horsnell@arm.com>
Fri, 15 Feb 2013 22:40:09 +0000 (17:40 -0500)
committerMatt Horsnell <Matt.Horsnell@arm.com>
Fri, 15 Feb 2013 22:40:09 +0000 (17:40 -0500)
commite88e7d88b9a9876ee040dad96acf3deabebe1fa7
tree54322d578272a21cd721788f25746cfbd88d94bb
parent64599080697a8db49b7e28609927bb4c1ed3c05e
o3: fix tick used for renaming and issue with range selection

Fixes the tick used from rename:
- previously this gathered the tick on leaving rename which was always 1 less
  than the dispatch. This conflated the decode ticks when back pressure built
  in the pipeline.
- now picks up tick on entry.

Added --store_completions flag:
- will additionally display the store completion tail in the viewer.
- this highlights periods when large numbers of stores are outstanding (>16 LSQ
  blocking)

Allows selection by tick range (previously this caused an infinite loop)
src/cpu/o3/commit_impl.hh
src/cpu/o3/decode_impl.hh
src/cpu/o3/dyn_inst.hh
src/cpu/o3/dyn_inst_impl.hh
src/cpu/o3/fetch_impl.hh
src/cpu/o3/iew_impl.hh
src/cpu/o3/lsq_unit_impl.hh
src/cpu/o3/rename_impl.hh
util/o3-pipeview.py