[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Conservative GC isn't safe
From: |
Pip Cet |
Subject: |
Re: Conservative GC isn't safe |
Date: |
Sat, 26 Nov 2016 19:08:44 +0000 |
On Sat, Nov 26, 2016 at 8:11 AM, Daniel Colascione <address@hidden> wrote:
> 1) mark_maybe_pointer looks only for exact matches on object start. It's
> perfectly legal for the compiler to keep an interior object pointer and
> discard the pointer to the object start.
There's a new, currently undocumented, GCC option called
-fkeep-gc-roots-live, which I think addresses this problem. My
understanding is previous versions of GCC did not in practice break
conservative GC (except for strings, which we handle specially for
this reason).
- Re: Conservative GC isn't safe, (continued)
- Re: Conservative GC isn't safe, Stefan Monnier, 2016/11/28
- Re: Conservative GC isn't safe, Eli Zaretskii, 2016/11/28
- Re: Conservative GC isn't safe, Stefan Monnier, 2016/11/28
- Re: Conservative GC isn't safe, Eli Zaretskii, 2016/11/28
- Re: Conservative GC isn't safe, Stefan Monnier, 2016/11/28
- Re: Conservative GC isn't safe, Ken Raeburn, 2016/11/28
- Re: Conservative GC isn't safe, Eli Zaretskii, 2016/11/28
- Re: Conservative GC isn't safe, Ken Raeburn, 2016/11/29
- Re: Conservative GC isn't safe, Paul Eggert, 2016/11/28
- Re: Conservative GC isn't safe, Stefan Monnier, 2016/11/27
Re: Conservative GC isn't safe,
Pip Cet <=