With JDK-8074096, the number of warnings in the product was reduced to a minimum. This enables the next step, which is turning on the respective compiler flags that turns warnings into errors. In the long run, this is the only way to keep the warnings from creeping back.

Since the product does not build 100% warning free, a system similar to the one introduced in JDK-8074096 is needed, in which individual libraries can be exempted from this flag, until such warnings are fixed.

Also, different versions of compilers can generate a different set of warnings. It is therefore necessary to be able to turn off this globally. Suggested solution is to add a --disable-warnings-as-errors flag to configure.