llvmcall deprecation warnings about groebner.jl HOT 4 OPEN

Thanks for reporting that. I'll switch to pointers.

Also, IMO, using assembly at all, let alone so much of it, is a red flag/strong code smell for such a high-level package.

I'm not excited about this as well. ATM I just try to keep llvmcalls in a single file, and maybe I ought to rethink their usefulness later.

from groebner.jl.

UPD: Now there is one more file where llvmcallss are used: https://github.com/sumiya11/Groebner.jl/blob/1966672ac52cba9f68f90685433abd21f4e584cc/src/utils/packed.jl

These llvmcalls grant around 15% performance improvement on one class of inputs.

Either compilers become smart enough to produce such code by themselves or I decide I do not care enough and delete all llvmcalls -- whivever comes first.

from groebner.jl.

To be more precise

using Groebner, AbstractAlgebra
k = GF(2^30+3)
C = [
           Groebner.Examples.HIV2(k=k),
           Groebner.Examples.Goodwin_with_weights(k=k),
           Groebner.Examples.yang1(k=k),
           Groebner.Examples.Cholera(k=k),
           Groebner.Examples.bayes148(k=k),
           Groebner.Examples.mayr42(k=k)
       ];

@time for c in C groebner(c); end

No llvmcalls :

98.660280 seconds (121.74 M allocations: 12.032 GiB, 4.05% gc time)

With llvmcalls :

92.756787 seconds (121.74 M allocations: 12.032 GiB, 4.25% gc time)

This is Julia Version 1.12.0-DEV.1076

from groebner.jl.

Either compilers become smart enough to produce such code by themselves or I decide I do not care enough and delete all llvmcalls -- whivever comes first.

#157

from groebner.jl.