libc++: First cut at <dynarray>
Hal Finkel
hfinkel at anl.gov
Wed Sep 18 16:18:39 PDT 2013
----- Original Message -----
> Hello,
>
> > Note that I didn't say "intractable", just "not trivial". I think
> > that's the case.
>
> Most likely everybody here knows this already, but since nobody
> mentioned it yet: Deciding whether
> a variable must be allocated on the heap or can be allocated on the
> stack is a problem that
> occurs quite often in VM-based languages (e.g. Java). The term to
> google for is Escape Analysis:
> <http://en.wikipedia.org/wiki/Escape_analysis>.
>
That's a good point. We don't need to necessarily see the corresponding decallocation call if we know that the pointer value does not escape.
-Hal
>
> Jonathan
>
>
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
>
--
Hal Finkel
Assistant Computational Scientist
Leadership Computing Facility
Argonne National Laboratory
More information about the cfe-commits
mailing list