derek/gem5
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

systemc: Track event sensitivities with a list instead of a set.

Browse Source 
It's totally legal to signal that an event happened to waiting
processes in any order we choose, but to match the order of events
which appears in the Accellera test golden output, we need to do things
in the order they did. This is less efficient, but will reduce the
number of false positives.

Change-Id: Ie2882249ae846991d627f5f688a9e89e629bb300
Reviewed-on: https://gem5-review.googlesource.com/c/12612
Reviewed-by: Gabe Black <gabeblack@google.com>
Maintainer: Gabe Black <gabeblack@google.com>
This commit is contained in:
Gabe Black
2018-09-10 17:23:22 -07:00
parent 110907bae1
commit e4ab67f717
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/systemc/core/event.hh
View File

@@ -30,7 +30,7 @@
#ifndef __SYSTEMC_CORE_EVENT_HH__
#define __SYSTEMC_CORE_EVENT_HH__
#include <set>
#include <list>
#include <string>
#include <vector>
@@ -93,8 +93,8 @@ class Event
return e->_gem5_event;
}
void addSensitivity(Sensitivity *s) const { sensitivities.insert(s); }
void delSensitivity(Sensitivity *s) const { sensitivities.erase(s); }
void addSensitivity(Sensitivity *s) const { sensitivities.push_back(s); }
void delSensitivity(Sensitivity *s) const { sensitivities.remove(s); }
private:
sc_core::sc_event *_sc_event;
@@ -107,7 +107,7 @@ class Event
ScEvent delayedNotify;
mutable std::set<Sensitivity *> sensitivities;
mutable std::list<Sensitivity *> sensitivities;
};
extern Events topLevelEvents;