search for: fastsc

...vening by writing two specialized passes that are needed to adjust SAFECode's instrumentation to what Nuno needs (one pass removes checks that are too expensive; the other inlines the fast checks to remove function call overhead). That code can still be found at http://sva.cs.illinois.edu/fastsc-llvm.tar.gz. I wrote a proposal for a common memory safety instrumentation infrastructure and sent it to llvm-commits. Would it be useful to send it to llvmdev as well for discussion, or has everyone who's already interested seen it? Having said all this, if exploit mitigation is the goal...

...t; two specialized passes that are needed to adjust SAFECode's > instrumentation to what Nuno needs (one pass removes checks that are too > expensive; the other inlines the fast checks to remove function call > overhead). That code can still be found at > http://sva.cs.illinois.edu/fastsc-llvm.tar.gz. > > I wrote a proposal for a common memory safety instrumentation > infrastructure and sent it to llvm-commits. Would it be useful to send > it to llvmdev as well for discussion, or has everyone who's already > interested seen it? > > Having said all this, if...

Hi Kostya, I'm also curious to know where Nuno is going with this, and the details of his design. I'm worried he might be reinventing the wheel. I'm also worried that he may be inventing a square wheel :) > I noticed your commits related to -fbounds-checking and have some questions. > The functionality of this new phase seems to (partially?) overlap with > AddressSanitizer

Hi Nuno, I noticed your commits related to -fbounds-checking and have some questions. The functionality of this new phase seems to (partially?) overlap with AddressSanitizer and SAFECode, so I am curious how would you compare the two existing tools with the new one. Earlier you wrote: >> So the main idea of this new flag is not for debugging, but rather for production. >> This means