summaryrefslogtreecommitdiff
path: root/util/plot_dram/lowp_dram_sweep_plot.py
diff options
context:
space:
mode:
authorGabe Black <gabeblack@google.com>2018-12-04 16:17:30 -0800
committerGabe Black <gabeblack@google.com>2018-12-18 11:48:30 +0000
commitc04578791ec20a5a41d02ed0ba8da10f0b29ca20 (patch)
tree86290083e62e4649ed4ae7c5c377667e1073ac20 /util/plot_dram/lowp_dram_sweep_plot.py
parent7fa4c946386e7207ad5859e8ade0bbfc14000d91 (diff)
downloadgem5-c04578791ec20a5a41d02ed0ba8da10f0b29ca20.tar.xz
systemc: Ensure resets and edges are notified when signaling a change.
Boolean sc_buffers (either pure bool or sc_dt::sc_logic) should signal positive and negative edges and resets even when their value doesn't change, unlike sc_signals. The spec doesn't actually say that and just mentions the value changed event, but it may have been implied that the other types of events also happen, they just made special mention of the value change event. This change moves some code around a bit so that when _signalChange() is called, if the underlying type is a boolean signal, it will automatically notify the appropriate edge event and signal any reset. Putting the functionality in _signalChange instead of delegating it to the sc_buffer lets us have a single template for sc_buffer and makes the base class template specialization handle whether the edge events exist, and if so which should be notified. Change-Id: Ic4ca86afc3fde6a9df5c15a0a7386e24ac89a9e2 Reviewed-on: https://gem5-review.googlesource.com/c/14916 Reviewed-by: Matthias Jung <jungma@eit.uni-kl.de> Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com>
Diffstat (limited to 'util/plot_dram/lowp_dram_sweep_plot.py')
0 files changed, 0 insertions, 0 deletions