#14704: Use GMP's mpz_t for bitsets
-------------------------------+--------------------------------------------
Reporter: Stefan | Owner: jason
Type: enhancement | Status: new
Priority: minor | Milestone: sage-wishlist
Component: misc | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by leif):
Well, the main disadvantage of using GMP's / MPIR's functions is that the
compiler has no chance to inline them / do further optimizations depending
on the context, and that you get another level of boxing (`mpz_t` points
to a structure containing a pointer to the actual data / the limbs).
So whether it's worth heavily depends on the application / use case.
But we could of course (probably dynamically) use different
implementations, whichever fits best in the specific case.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14704#comment:8>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
