-
Enhancement
-
Resolution: Fixed
-
P4
-
21, 22
-
b07
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8331099 | 21.0.4 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
When doing task JDK-8287325, I noticed that some stub routine tests are done inside function initialize_final_stubs(). See the code https://github.com/openjdk/jdk/blob/master/src/hotspot/share/runtime/stubRoutines.cpp#L325-L404
The test runs every time the debug VM is started.
I thought it's a usual convention that we'd better not to do functional tests on startup. Besides, we have the existing gtest framework for testing internal C++ modules.
Hence, I think it's worthing moving the stub test from initialize_final_stubs() to test/hotspot/gtest.
The test runs every time the debug VM is started.
I thought it's a usual convention that we'd better not to do functional tests on startup. Besides, we have the existing gtest framework for testing internal C++ modules.
Hence, I think it's worthing moving the stub test from initialize_final_stubs() to test/hotspot/gtest.
- backported by
-
JDK-8331099 Move the stub test from initialize_final_stubs() to test/hotspot/gtest
- Resolved