> On Feb 1, 2018, at 9:05 AM, Erik Joelsson <erik.joels...@oracle.com> wrote: > > Regarding warning chasing. I agree that we it's not feasible to chase down > every warning in every version of GCC, or any other toolchain, but I also > think that for platforms/configurations where people are actively developing > changes for OpenJDK, it makes sense to try to keep it clean. This helps > prevent new code from introducing warnings. For the configurations Oracle > use, we keep a strict -Werror policy because we want the code to be clean
Is it not the case that building on macOS requires -disable-warnings-as-errors? Or is that only the case on more recent macOS releases that used by Oracle? Alan
