-
Bug
-
Resolution: Fixed
-
P3
-
20
-
b20
After JDK-8294281, it is now possible to disable warnings for individual files instead for whole libraries. I used this opportunity to go through all disabled warnings in hotspot.
Any warnings that were only triggered in a few files were removed from hotspot as a whole, and changed to be only disabled for those files.
Some warnings didn't trigger in any file anymore, and could just be removed.
Overall, this reduced the number of disabled warnings by roughly half for gcc, clang and visual studio. The remaining warnings are sorted in "frequency", that is, the first listed warnings are triggered in the most number of files, while the last in the fewest number of files. So if anyone were to try to address the remaining warnings, it would make sense to chop of this list from the back.
Any warnings that were only triggered in a few files were removed from hotspot as a whole, and changed to be only disabled for those files.
Some warnings didn't trigger in any file anymore, and could just be removed.
Overall, this reduced the number of disabled warnings by roughly half for gcc, clang and visual studio. The remaining warnings are sorted in "frequency", that is, the first listed warnings are triggered in the most number of files, while the last in the fewest number of files. So if anyone were to try to address the remaining warnings, it would make sense to chop of this list from the back.
- relates to
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
JDK-8294467 Fix sequence-point warnings in Hotspot
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
JDK-8288293 Windows/gcc Port
-
- Draft
-
(2 relates to, 2 links to)