On May 25, 2012, at 3:43 PM, Evan Cheng wrote: > The primary concerns I have seen so far are "it doesn't serve the needs for > all memory safety techniques". Did I miss some other specific concern about > alloc_size attribute?
On another note, one part of Nuno's goal for the summer is to implement an array bound check elimination optimization of some sort. The longer term motivation for this is to support experimental safety enhancements that we may or may not end up doing in Objective-C - but I want to make sure that it is general enough to support Java or whatever other languages have implicit array bounds checks. How this eventually shakes out will depend on what the performance looks like, and that requires the optimization to be up in some simple way. I'm not trying to say that Nuno should do the wrong thing here or steam-roll it in, just saying that I agree with Evan's meta-point that "it doesn't serve the needs for all memory safety techniques" isn't super compelling for me. I definitely want this designed and implemented in the right way. -Chris _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
