-
Bug
-
Resolution: Fixed
-
P3
-
12
-
b13
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8328180 | 11.0.24-oracle | Ivan Bereziuk | P3 | Resolved | Fixed | b01 |
JDK-8329226 | 11.0.24 | Andrew Lu | P3 | Resolved | Fixed | b01 |
This is the first part towards a better framework in the build for handling compiler warnings. The basic idea is that we should have consistent way for all compilers to:
1) enable all (relevant) warnings
2) disable individual warnings, on a global scale (if 1 enables too much)
In particular, this means unifying the basic set of enabled warnings between hotspot and the JDK native libraries.
From that starting point, warnings can be disabled on a per-library fashion, if it does not make sense for that specific library. (Like how it's done today, but more consistently performed.)
This first part will just put most of the infrastructure in place, and strives to keep exactly the same warnings enabled or disabled for all code.
1) enable all (relevant) warnings
2) disable individual warnings, on a global scale (if 1 enables too much)
In particular, this means unifying the basic set of enabled warnings between hotspot and the JDK native libraries.
From that starting point, warnings can be disabled on a per-library fashion, if it does not make sense for that specific library. (Like how it's done today, but more consistently performed.)
This first part will just put most of the infrastructure in place, and strives to keep exactly the same warnings enabled or disabled for all code.
- backported by
-
JDK-8328180 Improved handling of compiler warnings in the build
-
- Resolved
-
-
JDK-8329226 Improved handling of compiler warnings in the build
-
- Resolved
-
- relates to
-
JDK-8211081 Solaris-X64 release build fails after JDK-8210988
-
- Closed
-
- links to
-
Commit openjdk/jdk11u-dev/29a08f77
-
Review(master) openjdk/jdk11u-dev/2606