Hello, There was P4 JDK-8275008 (https://bugs.openjdk.org/browse/JDK-8275008) about GKC 11 warning 'stringop-overflow' in gtest::Guarded Memory. It was fixed globally by disabling this warning for all openjdk gtests, although in fact the only test required this fix. Moreover, this wasn't a bug, because the test really does 'buffer overflow' to check memory guards then.
I realize that it's just a test, not a product, but anyway '-Wstringop-overflow' is not '-Wundef', and I don't think that disabling 'stringop-overflow' for all the tests is a good idea. Again, as far as I see, there are no other tests occurring this warning. Is it better to disable the warning locally in the test on upstream and add a comment describing expected behaviour regarding buffer overflow? Thanks, Roman
