-
Enhancement
-
Resolution: Fixed
-
P4
-
9
-
b93
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8156268 | 8u111 | Cheleswer Sahu | P4 | Closed | Fixed | b01 |
JDK-8147606 | 8u102 | Cheleswer Sahu | P4 | Resolved | Fixed | b01 |
JDK-8162065 | emb-8u111 | Unassigned | P4 | Resolved | Fixed | b01 |
In several places variables are initializaed in switch statements or the like, where the default case is decorated with ShouldNotReachHere() and the initialization is missing.
In the debug build, ShouldNotReachHere() can be suppressed, so the uninitialized value actually can cause problems.
In opt builds, not all tools recognize the ShouldNotReachHere properly.
This adds a row of initializations where I encountered problems and enables -Wuninitialized with linux gcc 4.8.
This would find most of these warnings. The flag works best in the product build, as it depends on compiler optimizations.
This unveiled some missing initializations in constructors, as in compile.hpp and oopMap.hpp, that can actually cause wrong behavior.
In the debug build, ShouldNotReachHere() can be suppressed, so the uninitialized value actually can cause problems.
In opt builds, not all tools recognize the ShouldNotReachHere properly.
This adds a row of initializations where I encountered problems and enables -Wuninitialized with linux gcc 4.8.
This would find most of these warnings. The flag works best in the product build, as it depends on compiler optimizations.
This unveiled some missing initializations in constructors, as in compile.hpp and oopMap.hpp, that can actually cause wrong behavior.
- backported by
-
JDK-8147606 Fix initializations before ShouldNotReachHere() etc. and enable -Wuninitialized on linux.
-
- Resolved
-
-
JDK-8162065 Fix initializations before ShouldNotReachHere() etc. and enable -Wuninitialized on linux.
-
- Resolved
-
-
JDK-8156268 Fix initializations before ShouldNotReachHere() etc. and enable -Wuninitialized on linux.
-
- Closed
-