search for: onlyaccessesargmem

Hi James, Thank you for the response. I understand the concern about malloc/free hooks. Could we detect that a program has setup malloc hooks (assuming we're in a whole program compilation) and make assumptions (such as onlyAccessesArgMem()) when the program hasn't setup malloc hooks? Using a command line flag could be one option too. I'm currently working on a program where having these attributes could help GlobalsAA give significantly more precise results. Considering that this info is propagated to the caller, its calle...

Hi, GlobalsAA, during propagation of mod-ref behavior in the call graph, looks at library functions (in GlobalsAAResult::AnalyzeCallGraph: F->isDeclaration() check), for attributes, and if the function does not have the onlyReadsMemory attribute set, forgets it. I noticed that library functions such as malloc/realloc do not have the attributes doesNotAccessMemory or onlyReadsMemory

...n at compilertree.com > > wrote: > > Hi James, > > Thank you for the response. I understand the concern about > malloc/free hooks. Could we detect that a program has setup malloc > hooks (assuming we're in a whole program compilation) and make > assumptions (such as onlyAccessesArgMem()) when the program hasn't > setup malloc hooks? Using a command line flag could be one option > too. > > I'm currently working on a program where having these attributes > could help GlobalsAA give significantly more precise results. > Considering that this info is propa...