After (a lot) more work, including looking for MWE (see
https://godbolt.org/z/38nnaEcrf), I am confident this is a bug which
has already been resolved:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111415.
The bug only occurs when optimisation is enabled (-O1 to -O3 at
least), on GCC 12.4, 13.1--13
On 5/9/25 03:09, Stephen Wade wrote:
The literanger package is no longer passing on CRAN
(https://CRAN.R-project.org/package=literanger) due to array-bound
warnings in GCC 13.3 and 14.2 (more details below).
This _looks_ to me like one of either a) a compiler bug, b) a false
positive, or c) (v
> On 9 May 2025, at 19:29, Kevin Ushey wrote:
>
> Hopefully a member of the CRAN team will tell me I'm wrong, but I
> think whether or not there is a compiler bug is ultimately irrelevant
> -- packages on CRAN must compile cleanly even with potentially-buggy
> development versions of compilers.
Hopefully a member of the CRAN team will tell me I'm wrong, but I
think whether or not there is a compiler bug is ultimately irrelevant
-- packages on CRAN must compile cleanly even with potentially-buggy
development versions of compilers.
So, whether or not there is a bug in gcc is moot -- you'll
В Fri, 9 May 2025 11:09:22 +1000
Stephen Wade пишет:
> inlined from ‘std::vector literanger::adjust_pvalues(const
> std::vector&)’ at ../src/literanger/utility_math.h:99:48:
> /usr/include/c++/13/bits/stl_algobase.h:437:30: warning: ‘void*
> __builtin_memmove(void*, const void*, long unsigned
The literanger package is no longer passing on CRAN
(https://CRAN.R-project.org/package=literanger) due to array-bound
warnings in GCC 13.3 and 14.2 (more details below).
This _looks_ to me like one of either a) a compiler bug, b) a false
positive, or c) (very unlikely) something in the standard l
