From f2892fd5bc3c8468ac1d40f449a988c2670397b6 Mon Sep 17 00:00:00 2001 From: "Erin (Jianghua) Le" Date: Wed, 6 Nov 2024 10:40:07 -0800 Subject: [PATCH] misc: update RELEASE-NOTES.md for simInsts and simOps (#1750) This PR updates RELEASE-NOTES.md to say that simInsts and simOps have been modified such that they now reset to 0 when m5.stats.reset() is called. --- RELEASE-NOTES.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.md index a97bdec6aa..f310ccde31 100644 --- a/RELEASE-NOTES.md +++ b/RELEASE-NOTES.md @@ -7,6 +7,11 @@ * It returns if the stride does not match, as opposed to issuing prefetching using the new stride --- the previous, incorrect behavior. * Returns if the new stride is 0, indicating multiple reads from the same cache line. +* The [behavior of the statistics `simInsts` and `simOps` has been changed](https://github.com/gem5/gem5/pull/1615). + * They now reset to zero when m5.stats.reset() is called. + * Previously, they incorrectly did not reset and would increase monotonically throughout the simulation. + * The statistics `hostInstRate` and `hostOpRate` are also affected by this change, as they are calculated using simInsts and simOps respectively. + ### Multiple RubySystem objects in a simulation Simulation configurations can now create multiple `RubySystem`s in the same simulation. @@ -27,6 +32,7 @@ The complete list of changes are: * You may no longer call `RubySystem::getBlockSizeBytes()`, `RubySystem::getBlockSizeBits()`, etc. You must have a pointer to the `RubySystem` you are a part of and call, for example, `ruby_system->getBlockSizeBytes()`. * `MessageBuffer::enqueue()` has two new parameters indicating if the `RubySystem` has randomization and warmup enabled. You must explicitly specify these values now. + # Version 24.0 gem5 Version 24.0 is the first major release of 2024.