Searched hist:11181 (Results 1 - 7 of 7) sorted by relevance
/gem5/src/systemc/tests/systemc/bugs/constructor_throw/ | ||
H A D | constructor_throw.cpp | 12876:e332bbd21d47 Wed Jun 13 21:41:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Remove references to internal constants from the tests. The tests were referring to constants defined in the Accellera systemc implementation which identified various log message types. This change replaces those (sometimes quite long) string constants with their actual value. This doesn't make that interface any more fragile since the constant value won't track between the Accellera version and this one, but it does make its fragility more explicit by using the value directly. If in the future we decide to hide the magical nature of those particular string constants, we could make them into our own constants in the implementation. Regardless, the tests shouldn't refer to internal details of the implementation. Change-Id: I116a7407fcac49367649b250683117f3ccf4f9ed Reviewed-on: https://gem5-review.googlesource.com/11181 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
/gem5/src/systemc/tests/systemc/communication/sc_buffer/test02/ | ||
H A D | sc_buffer_edge_reset.cpp | 12876:e332bbd21d47 Wed Jun 13 21:41:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Remove references to internal constants from the tests. The tests were referring to constants defined in the Accellera systemc implementation which identified various log message types. This change replaces those (sometimes quite long) string constants with their actual value. This doesn't make that interface any more fragile since the constant value won't track between the Accellera version and this one, but it does make its fragility more explicit by using the value directly. If in the future we decide to hide the magical nature of those particular string constants, we could make them into our own constants in the implementation. Regardless, the tests shouldn't refer to internal details of the implementation. Change-Id: I116a7407fcac49367649b250683117f3ccf4f9ed Reviewed-on: https://gem5-review.googlesource.com/11181 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
/gem5/src/systemc/tests/systemc/communication/sc_signal/check_writer/test16/ | ||
H A D | test16.cpp | 12876:e332bbd21d47 Wed Jun 13 21:41:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Remove references to internal constants from the tests. The tests were referring to constants defined in the Accellera systemc implementation which identified various log message types. This change replaces those (sometimes quite long) string constants with their actual value. This doesn't make that interface any more fragile since the constant value won't track between the Accellera version and this one, but it does make its fragility more explicit by using the value directly. If in the future we decide to hide the magical nature of those particular string constants, we could make them into our own constants in the implementation. Regardless, the tests shouldn't refer to internal details of the implementation. Change-Id: I116a7407fcac49367649b250683117f3ccf4f9ed Reviewed-on: https://gem5-review.googlesource.com/11181 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
/gem5/src/systemc/tests/systemc/kernel/phase_callbacks/test04/ | ||
H A D | register_phase_callbacks.cpp | 12876:e332bbd21d47 Wed Jun 13 21:41:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Remove references to internal constants from the tests. The tests were referring to constants defined in the Accellera systemc implementation which identified various log message types. This change replaces those (sometimes quite long) string constants with their actual value. This doesn't make that interface any more fragile since the constant value won't track between the Accellera version and this one, but it does make its fragility more explicit by using the value directly. If in the future we decide to hide the magical nature of those particular string constants, we could make them into our own constants in the implementation. Regardless, the tests shouldn't refer to internal details of the implementation. Change-Id: I116a7407fcac49367649b250683117f3ccf4f9ed Reviewed-on: https://gem5-review.googlesource.com/11181 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
/gem5/src/systemc/tests/systemc/kernel/process_control/reset/method_reset_throw/ | ||
H A D | sc_method_reset_throw.cpp | 12876:e332bbd21d47 Wed Jun 13 21:41:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Remove references to internal constants from the tests. The tests were referring to constants defined in the Accellera systemc implementation which identified various log message types. This change replaces those (sometimes quite long) string constants with their actual value. This doesn't make that interface any more fragile since the constant value won't track between the Accellera version and this one, but it does make its fragility more explicit by using the value directly. If in the future we decide to hide the magical nature of those particular string constants, we could make them into our own constants in the implementation. Regardless, the tests shouldn't refer to internal details of the implementation. Change-Id: I116a7407fcac49367649b250683117f3ccf4f9ed Reviewed-on: https://gem5-review.googlesource.com/11181 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
/gem5/src/systemc/tests/systemc/kernel/sc_time/test19/ | ||
H A D | test19.cpp | 12876:e332bbd21d47 Wed Jun 13 21:41:00 EDT 2018 Gabe Black <gabeblack@google.com> systemc: Remove references to internal constants from the tests. The tests were referring to constants defined in the Accellera systemc implementation which identified various log message types. This change replaces those (sometimes quite long) string constants with their actual value. This doesn't make that interface any more fragile since the constant value won't track between the Accellera version and this one, but it does make its fragility more explicit by using the value directly. If in the future we decide to hide the magical nature of those particular string constants, we could make them into our own constants in the implementation. Regardless, the tests shouldn't refer to internal details of the implementation. Change-Id: I116a7407fcac49367649b250683117f3ccf4f9ed Reviewed-on: https://gem5-review.googlesource.com/11181 Reviewed-by: Gabe Black <gabeblack@google.com> Maintainer: Gabe Black <gabeblack@google.com> |
/gem5/src/arch/arm/ | ||
H A D | table_walker.cc | 11181:4daf60db14d7 Thu Oct 29 08:48:00 EDT 2015 Nathanael Premillieu <nathananel.premillieu@arm.com> arm: Add secure flag to TableWalker request when needed |
Completed in 36 milliseconds