Dirk
Thanks for a very helpful reply. I'll simplify my return values.

I mentioned Intel with rhub2 in my earlier post here, but I'm sorry
that was somewhat buried. Debugging is somewhere between painful and
impossible when my only check is submitting to CRAN!

Also, I had tried valgrind, but that got stuck in Linux on what I
assumed was an unrelated "unhandled instruction" error wrt OpenBLAS.
That appeared unrelated, but maybe we need to factor it in as a
possible interaction with RcppArmadillo. Strangely valgrind sticks on
this --
==2242833== valgrind: Unrecognised instruction at address 0x57d3650.
==2242833==    at 0x57D3650: dot_compute (in
/opt/OpenBLAS/lib/libopenblas_skylakexp-r0.3.23.dev.so)
-- even after I have set options(matprod="internal") in R, so
something else (RcppArmadillo?) must be trying to use OpenBLAS.

Murray

On Mon, Mar 4, 2024 at 1:58 AM Dirk Eddelbuettel <e...@debian.org> wrote:
>
>
> And "beauty" (ahem) of discussion scattered over two mailing lists: I now see
> you have a testbed via rhub2 (good) even though it does not reproduce (hm...).
>
> So you could still try the suggested simplication.
>
> Cheers, Dirk
>
> --
> dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel

Reply via email to