#19883: Let PARI handle its own stack
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-7.0
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers:
Authors: Jeroen Demeyer | Work issues:
Report Upstream: Reported | Commit:
upstream. No feedback yet. | 435a4fe79fb3b2d7a652c4d512bc6531c4762ab3
Branch: | Stopgaps:
u/jdemeyer/let_pari_handle_its_own_stack|
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by vbraun):
Just run malloc (without free) in a for-loop, I'm pretty sure that it
stops before the entire addressing space is used up.
Thats also a pretty weird use case, a process allocates memory but doesn't
use it. Why should the virtual memory system cater to that and do all the
extra accounting? If you don't need memory then don't ask for it. And in
the extremely special case where you want to implement your own memory
manager in user space there is still mmap(MAP_NORESERVE).
--
Ticket URL: <http://trac.sagemath.org/ticket/19883#comment:25>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
