Searched hist:12041 (Results 1 - 5 of 5) sorted by relevance
/gem5/src/systemc/core/ | ||
H A D | kernel.hh | diff 12990:19d91b53e04e Fri Jul 20 22:23:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Make some functions of the kernel static. This makes it possible to call them without having to have a kernel instance available. The kernel is a singleton anyway, so there should only ever be a single instance of any of these values. Change-Id: I3610d60cc72e9f3114997fe63db94b96ccaac3cd Reviewed-on: https://gem5-review.googlesource.com/12041 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
H A D | sc_main.cc | diff 12990:19d91b53e04e Fri Jul 20 22:23:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Make some functions of the kernel static. This makes it possible to call them without having to have a kernel instance available. The kernel is a singleton anyway, so there should only ever be a single instance of any of these values. Change-Id: I3610d60cc72e9f3114997fe63db94b96ccaac3cd Reviewed-on: https://gem5-review.googlesource.com/12041 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
H A D | kernel.cc | diff 12990:19d91b53e04e Fri Jul 20 22:23:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Make some functions of the kernel static. This makes it possible to call them without having to have a kernel instance available. The kernel is a singleton anyway, so there should only ever be a single instance of any of these values. Change-Id: I3610d60cc72e9f3114997fe63db94b96ccaac3cd Reviewed-on: https://gem5-review.googlesource.com/12041 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
/gem5/src/python/pybind11/ | ||
H A D | event.cc | diff 12041:52b3b120dbc0 Wed May 10 05:57:00 EDT 2017 Andreas Sandberg <andreas.sandberg@arm.com> python: Fix PyEvent reference counting bug The current implementation of reference counting for PyEvents only partially works. The native object is currently kept alive while it is in the event queue. However, if the Python object goes out of scope, the Python side of this object is garbage collected which leaves a "dangling" native object. This results in confusing error messages where PyBind is unable to find the Python implementation of an event when it is triggered. Implement reference counting using the generalized reference counting API instead. Change-Id: I4e8e04abc4f61dff238d718065f5371e73b38ab3 Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-on: https://gem5-review.googlesource.com/3222 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
/gem5/src/python/m5/ | ||
H A D | event.py | diff 12041:52b3b120dbc0 Wed May 10 05:57:00 EDT 2017 Andreas Sandberg <andreas.sandberg@arm.com> python: Fix PyEvent reference counting bug The current implementation of reference counting for PyEvents only partially works. The native object is currently kept alive while it is in the event queue. However, if the Python object goes out of scope, the Python side of this object is garbage collected which leaves a "dangling" native object. This results in confusing error messages where PyBind is unable to find the Python implementation of an event when it is triggered. Implement reference counting using the generalized reference counting API instead. Change-Id: I4e8e04abc4f61dff238d718065f5371e73b38ab3 Signed-off-by: Andreas Sandberg <andreas.sandberg@arm.com> Reviewed-by: Curtis Dunham <curtis.dunham@arm.com> Reviewed-on: https://gem5-review.googlesource.com/3222 Reviewed-by: Jason Lowe-Power <jason@lowepower.com> |
Completed in 30 milliseconds