On 01/03/2023 18:33, Manuel López-Ibáñez wrote:
Dear CRAN Team,
I believe those are false positives. All pointers are updated after
realloc. I have verified that this is the case not only at this point
but also at every realloc call.
It may be this compiler bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104215
I believe this warning may eventually get moved out of -Wall because it
has become too noisy in GCC 12:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=Wuse-after-free
Are you aware that eaf still gives a warning with the latest gcc 13
snapshot? There are 3 CRAN packages which no longer warn with gcc 13,
but yours is not one of them. And none that warn with gcc 13 but not
gcc 12.
gcc 13 is in final bug-fixing and was expected to be released by now.
We don't have time to study maintainers' C++ code so have to let this
pass without accepting that it is the compiler and not your fault. We
would like you to file a bug report specifically about your code and get
agreement from the GCC developers that this is their bug.
Best wishes,
Manuel.
On 01/03/2023 17:02, Prof Brian Ripley wrote:
Dear maintainer,
Please see the problems shown on
<https://cran.r-project.org/web/checks/check_results_eaf.html>.
Please correct before 2023-03-15 to safely retain your package on CRAN.
The CRAN Team
--
Brian D. Ripley, rip...@stats.ox.ac.uk
Emeritus Professor of Applied Statistics, University of Oxford
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
