Both Singular and libsingular.so use omalloc, which is some kind of bump
allocator (currently being given multithreading support BTW). It's much
faster than xmalloc for that application (libsingular and Singular use it
for allocating the objects in the linked list implementations of sparse
dist
Actually, I think the issue here is that there isn't actually a division
happening, rather, it *is* doing the unit check and inverse of unit
calculation within numerator(); but still moves to the fractionfield. When
numerator(), on the fractionfield element is called, eventually the
function in
On Mon, Jun 17, 2019 at 9:01 AM Simon King wrote:
>
> Hi!
>
> On 2019-06-16, Dima Pasechnik wrote:
> > libsingular interface is a mess, cf e.g.
> > https://trac.sagemath.org/ticket/27508
>
> Singular uses a peculiar memory manager that is optimized for Gröbner
> basis computations. If that memory
Hi!
On 2019-06-16, Dima Pasechnik wrote:
> libsingular interface is a mess, cf e.g.
> https://trac.sagemath.org/ticket/27508
Singular uses a peculiar memory manager that is optimized for Gröbner
basis computations. If that memory manager is replaced by ordinary
malloc (which makes sense for debu
