[m-dev.] [Gc] Mercury and GCC split stacks

Hans Boehm boehm at acm.org
Fri Sep 5 14:46:39 AEST 2014

I think this will require work to correctly scan such stacks.  AFAIK, the
collector currently assumes that thread stacks are contiguous.  The current
thread stopping code may also need work to perform reasonably for large
numbers of (hopefully mostly blocked) threads.


On Thu, Sep 4, 2014 at 7:43 PM, Paul Bone <paul at bone.id.au> wrote:

> On Fri, Sep 05, 2014 at 10:01:26AM +1000, Julien Fischer wrote:
> >
> > Hi,
> >
> > Has anyone tried Mercury (particularly the high-level C grades) with
> > GCC's split stacks capability?  See: <
> https://gcc.gnu.org/wiki/SplitStacks>.
> >
> The trade offs seem interesting, not that they're trying to economise on
> address space usage, especially on 32bit systems.  On a 64bit system this
> isn't a big deal for C programs as only the parts of the stack that
> actually
> get used get mapped to actual physical pages.
> There may also be interesting interactions with the Boehm collector.  Will
> BoehmGC be able to scan these stacks?
> I've cross-posted this to the Boehm GC list as it may be interesting for
> the GC's developers.
> --
> Paul Bone
> _______________________________________________
> bdwgc mailing list
> bdwgc at lists.opendylan.org
> https://lists.opendylan.org/mailman/listinfo/bdwgc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/developers/attachments/20140904/60373b90/attachment.html>

More information about the developers mailing list