On Wed, 6 Sep 2023 14:29:56 GMT, Antonios Printezis <to...@openjdk.org> wrote:
> The build failure happens when building on RISC-V with GCC 12.3. Is there a > better way to address this than disabling the stringop-overflow warnings for > the two files in question? It seems to be complaining about atomic increment of a data member, which is really weird. Atomic::add(&_claimed, flushed); When we saw this warning in other places it was because we were passing a pointer that was known to be null on some (not supposed to be reachable) code paths. I don't see how that can be what's going on here though. There's an Atomic::sub on the same data member a few lines later. Does that get warned about? And why these? I'm pretty sure there are other places where we do the same thing. (I'm assuming this warning isn't showing up elsewhere.) Disabling the warning for this file feels a bit too much like voodoo, though might be all we've got right now. ------------- PR Comment: https://git.openjdk.org/jdk/pull/15593#issuecomment-1718105899
