On 26 March 2024 at 09:37, Dirk Eddelbuettel wrote:
|
| Avi,
|
| That was a hickup and is now taken care of. When discussing this (off-line)
| with Jeroen we (rightly) suggested that keeping an eye on
Typo, as usual, "he (rightly) suggested". My bad.
D.
|
|
Hi Jesse,
What I've done is to use a mix of compile-time detection of compiler SIMD
support and run-time detection of SIMD hardware support. At package load,
SIMD-specific versions of functions are installed in a symbol table. It's
not perfect and it can be hard to support evolving platforms,
On 3/26/24 10:53, jesse koops wrote:
Hello R-package-devel,
I recently got inspired by the rcppsimdjson package to try out simd
registers. It works fantastic on my computer but I struggle to find
information on how to make it portable. It doesn't help in this case
that R and Rcpp make
On 26 March 2024 at 10:53, jesse koops wrote:
| How can I make this portable and CRAN-acceptable?
But writing (or borrowing ?) some hardware detection via either configure /
autoconf or cmake. This is no different than other tasks decided at
install-time.
Start with 'Writing R Extensions', as
Avi,
That was a hickup and is now taken care of. When discussing this (off-line)
with Jeroen we (rightly) suggested that keeping an eye on
https://contributor.r-project.org/svn-dashboard/
is one possibility to keep track while we have no status alert system from
CRAN. I too was quite
On 25 March 2024 at 11:12, Jairo Hidalgo Migueles wrote:
| I'm reaching out to seek some guidance regarding the storage of relatively
| large data, ranging from 10-40 MB, intended for use within an R package.
| Specifically, this data consists of regression and random forest models
| crucial for
Hello R-package-devel,
I recently got inspired by the rcppsimdjson package to try out simd
registers. It works fantastic on my computer but I struggle to find
information on how to make it portable. It doesn't help in this case
that R and Rcpp make including Cpp code so easy that I have never had
