-
Bug
-
Resolution: Fixed
-
P3
-
24
-
b14
Currently, we issue -Wno-unused for all files in gcc, which is a rather big sledgehammer to get rid of some warnings that proliferate in a few areas of the build.
We should instead leave -Wunused turned on (as done by -Wall) and use a much more fine-grained approach to disabling specific warnings in specific files or libraries.
We should instead leave -Wunused turned on (as done by -Wall) and use a much more fine-grained approach to disabling specific warnings in specific files or libraries.
- relates to
-
JDK-8342682 Errors related to unused code on Windows after 8339120 in dt_shmem jdwp security and jpackage
- In Progress
-
JDK-8342869 Errors related to unused code on Windows after 8339120 in awt
- In Progress
-
JDK-8342870 Errors related to unused code on Windows after 8339120 in accessibility
- In Progress
-
JDK-8339156 Use more fine-granular clang unused warnings
- Resolved
-
JDK-8339237 RISC-V: Builds fail after JDK-8339120
- Resolved
- links to
-
Commit(master) openjdk/jdk/362f9ce0
-
Review(master) openjdk/jdk/20733
(2 links to)