On Tue, 18 Oct 2022 15:21:38 GMT, Aleksey Shipilev <sh...@openjdk.org> wrote:
> Since the warning seems to be caused by the popular header, it is likely to > break some other platforms/files through the different include paths from the > different compilation units. The warning also looks fairly dubious, and > probably is GCC bug, as it does not trigger with higher GCCs? Because of > this, I suggest we add `strict-overflow` back to the global warning exclusion > list Good suggestion. Updated. Thanks. ------------- PR: https://git.openjdk.org/jdk/pull/10738
