On Fri, 17 Nov 2023 00:31:36 GMT, Mikael Vidstedt wrote:
> In JDK-8319818 the stringop-overflow warnings were disabled for linux-aarch64
> (fastdebug). With the changes in JDK-8319883 additional stringop-overflow
> warnings are produced with GCC 13.2.0, this time for linux-x64-zero
>
On Fri, 17 Nov 2023 00:31:36 GMT, Mikael Vidstedt wrote:
> In JDK-8319818 the stringop-overflow warnings were disabled for linux-aarch64
> (fastdebug). With the changes in JDK-8319883 additional stringop-overflow
> warnings are produced with GCC 13.2.0, this time for linux-x64-zero
>
On Fri, 17 Nov 2023 15:36:29 GMT, Magnus Ihse Bursie wrote:
> Looks okay from a build perspective. In the end, I guess some hotspot
> developers need to weigh in if this is acceptable.
>
> I presume you have tried to analyze what makes the Thread:current access
> different in these files, so
On Fri, 17 Nov 2023 00:31:36 GMT, Mikael Vidstedt wrote:
> In JDK-8319818 the stringop-overflow warnings were disabled for linux-aarch64
> (fastdebug). With the changes in JDK-8319883 additional stringop-overflow
> warnings are produced with GCC 13.2.0, this time for linux-x64-zero
>
In JDK-8319818 the stringop-overflow warnings were disabled for linux-aarch64
(fastdebug). With the changes in JDK-8319883 additional stringop-overflow
warnings are produced with GCC 13.2.0, this time for linux-x64-zero
(fastdebug). The warnings are related to GCC thinking JavaThread:current
