search for: extractmalloccall

...r did I completely misunderstand > you? no, I'm thinking that SAFECode won't need to look at or worry about the attribute at all, because the LLVM methods will know about it and serve up the appropriate info. Take a look at Analysis/MemoryBuiltins.h. In spite of the names, things like extractMallocCall are dealing with "malloc like" functions, such as C++'s "new" as well as malloc. Similarly for calloc. So you could use those right now to extract "malloc" and "calloc" sizes. If alloc_size is implemented, presumably these would just magically start to...

On 5/25/12 2:16 AM, Duncan Sands wrote: > Hi John, > >>>> I'm implementing the alloc_size function attribute in clang. >>> does anyone actually use this attribute? And if they do, can it >>> really buy >>> them anything? How about "implementing" it by ignoring it! >> > ... >> >> Currently, SAFECode has a pass which

...erstand you? > > no, I'm thinking that SAFECode won't need to look at or worry about > the attribute at all, because the LLVM methods will know about it and > serve up the appropriate info. Take a look at > Analysis/MemoryBuiltins.h. In spite of the names, things like > extractMallocCall are dealing with "malloc like" functions, such as > C++'s "new" as well as malloc. Similarly for calloc. So you could > use those right now to extract "malloc" and "calloc" sizes. If > alloc_size is implemented, presumably these would just mag...