Thanks to the encouragement of Brodie Gaslam and Tomas Kalibera (private
email), I was able to hack the code to avoid the warnings.
The code in question had the following structure:
int inibits = -1, bit;
for( j = powers; j; j >>= 1 ) ++inibits;
memcpy(pv, pini, inibits*sizeof(*pini
At the risk of only being mildly (if at all) helpful, I was able
to reproduce your warnings on Rhub, which has the same compiler,
with:
rhub::check('cubature_2.0.4.1.tar.gz', platform='windows-x86_64-release')
Absent feedback from CRAN you could try tweaking your code so that
it does not prod
On 10 May 2021 at 13:01, Balasubramanian Narasimhan wrote:
| It appears that I am unable to get beyond the auto-check service. Any
| suggestions?
I have tried for several weeks, and four emails, to get an answer concerning
an auto-archived submission. Ironically, it aimed to address the very 'e
I submitted a minor update of cubature (suggesting rmarkdown for
vignettes) and received a message that the package generated warnings.
However, the warnings were noted to be untrustworthy (see email below).
I noted this in the submission comments as well as the reply to the
auto-check email.
