Searched hist:13048 (Results 1 - 2 of 2) sorted by relevance
| /gem5/src/systemc/core/ | ||
| H A D | sc_export.cc | diff 13048:9ae0bf1b32e6 Wed Aug 08 22:31:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Implement sc_export. This change ignores the rule that sc_exports all have to be bound exactly once and only by the end of elaboration. If it's bound more than once, then the earlier binding will be overwritten, and if it's not bound at all then it will act like a null pointer. To accomodate doing those checks in the future, the sc_export_base constructor and destructor are in the .cc file even though they do very little so that they can be extended to track a list of all exports which exist. Change-Id: Ie9a3416b8fa87bca55bc9f87f3238c4de3c2e729 Reviewed-on: https://gem5-review.googlesource.com/12079 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
| /gem5/src/systemc/ext/core/ | ||
| H A D | sc_export.hh | diff 13048:9ae0bf1b32e6 Wed Aug 08 22:31:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Implement sc_export. This change ignores the rule that sc_exports all have to be bound exactly once and only by the end of elaboration. If it's bound more than once, then the earlier binding will be overwritten, and if it's not bound at all then it will act like a null pointer. To accomodate doing those checks in the future, the sc_export_base constructor and destructor are in the .cc file even though they do very little so that they can be extended to track a list of all exports which exist. Change-Id: Ie9a3416b8fa87bca55bc9f87f3238c4de3c2e729 Reviewed-on: https://gem5-review.googlesource.com/12079 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
Completed in 14 milliseconds