On Wed, Jan 8, 2014 at 11:20 PM, William ML Leslie < [email protected]> wrote:
> I should ask, before I start thinking about the valid 'fixes': a little > while ago, I was thinking about the class of region problems where we could > insert the equivalent malloc/free calls and knew that we didn't need a > collection pass. There's even a class of region problem where we can do > bump allocation on a gcless heap. Assuming that such cases don't lead to > additional code paths in the presence of region polymorphism, are those > techniques you wanted to consider? > I'm actually not aware that either of these is possible. Regions don't really facilitate bump allocation, because regions r1 < r2 can be simultaneously live and in scope, and allocation can proceed in either. The *regions* are nested, but the *allocations* are not. If you are familiar with GCC: regions are not obstacks. I'm also not familiar with any region analysis that makes it safe to insert explicit calls to free. Either the region is live, in which case we cannot free it explicitly, or it is dead, in which case there is no need to free it at the source code level. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
