Svadev mailing list

[Matthew Wala <wala1 AT illinois.edu>]

On Mon, Jul 11, 2011 at 11:40 AM, John Criswell 
<criswell AT illinois.edu>
 wrote:
>
> So, you have a couple of options for how to fix this:
>
> 1) Modify the StdLibPass to mark the DSNode of the static memory with the
> External flag.
> 2) Modify SAFECode to register the memory returned by these functions into a
> pool.
> 3) Modify SAFECode's CompleteChecks pass to not make these memory objects
> complete.
>
> Option 2 is probably the best as it will provide the greatest safety.
>

Is there a pass that does something similar already, or
(hypothetically) would implementing Option 2 best belong in a new
pass, in, say, lib/InsertPoolChecks?
Doesn't registering the object require knowing its size? I'm not sure
that there's a portable way to get the size of the internal static
memory that holds the return values of these functions.

Matt
- Hide quoted text -

>
> It may also be worth enhancing the exactcheck optimization pass to treat
> these functions like allocators.  I'd be willing to bet that many of these
> memory objects are only accessed within the function in which they are
> called and would benefit from the exactcheck optimization.
>
> -- John T.
>