search for: fastcheck

Hi, apart from the mmap(2)ed DBM files that Samba uses, are they any cases where Samba will *modify* data files without setting the mtime ? I have issues with rsync not seeing changes to Samba exported files (md5sum don't match). The mtime is however in the very distant past (say 2004), but the content seems to have changed. I don't think it's a data integrity issue. Any idea ?

...use this attribute? And if they do, can it really buy > them anything? How about "implementing" it by ignoring it! Tools like ASan and SAFECode *could* use this attribute to determine the size of memory objects created by allocators. This is needed for things like SAFECode's fastcheck optimization (which replaces expensive checks that need to lookup object bounds with a simpler check that has the object bounds passed in as arguments) as well as its instrumentation to register heap object bounds with the SAFECode run-time. Currently, SAFECode has a pass which just recognizes...

Hi Nuno, > 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! Ciao, Duncan. This > attribute exists in gcc since version 4.3. > The attribute specifies that a function returns a buffer with the size > given by the

Hi, I'm implementing the alloc_size function attribute in clang. This attribute exists in gcc since version 4.3. The attribute specifies that a function returns a buffer with the size given by the multiplication of the specified arguments. I would like to add new metadata to pass this information to LLVM IR. For example, take the following C code: void* my_calloc(size_t, size_t)

...ch optimization will fire often enough to pay the price for the added complexity of the implementation. It would be interesting to see statistics on some huge app. --kcc > to determine the > size of memory objects created by allocators. This is needed for things > like SAFECode's fastcheck optimization (which replaces expensive checks > that need to lookup object bounds with a simpler check that has the > object bounds passed in as arguments) as well as its instrumentation to > register heap object bounds with the SAFECode run-time. > > Currently, SAFECode has a pass w...