similar to: [LLVMdev] SAFECode and CMake?

On 9/9/11 1:08 PM, Jack Howarth wrote: > Are there any plans to add CMake support to the build of > SAFECode? No, there are no current plans to do so. Is not having CMake support a show-stopper for you? I imagine adding support for it would be straightforward. > Also are there any current instructions for building > llvm/clang with SAFECode support from current svn? Yes.

Dear All, We have a new release of Clang with SAFECode technology for detecting memory safety errors. Memory safety checking (SAFECode for short) can be turned on with a single command line switch to clang/clang++. The SAFECode techniques do not change the behavior of the clang/clang++ compilers in any way when the switch is turned off, so this can be used as a drop-in replacement for

Török Edwin wrote: > [snip] > > I applied the attached patch to make it compile on my box (Debian > x86_64), only to find out that x86_64 is not supported :( > This architecture is not supported by the pool allocator! > Aborted > Thanks for the patch. What options do I give to the patch command to apply it to the source code? Although there's no documentation about

yiqiuping1986 wrote: > Hi， John Criswell！ > You have said to me that SAFECode had not been maintained for several > years, Just to clarify, SAFECode *has* been and *is* maintained (primarily by me). The release_26 branch in the SVN repository works with LLVM 2.6, and mainline is working (with some regressions) with the upcoming LLVM 2.7. You can subscribe to the SVA Commits mailing list

Hi， John Criswell！ You have said to me that SAFECode had not been maintained for several years, now I have submitted my proposal for updating the SAFCode project to the new LLVM APIs. If you are still interested in the topic and willing to guid my project, I will be very happy. Now I'm waiting for you comments. Here is my proposal:

On Sep 10, 2011, at 10:00 AM, John Criswell wrote: > On 9/9/11 1:08 PM, Jack Howarth wrote: >> Are there any plans to add CMake support to the build of >> SAFECode? > > No, there are no current plans to do so. Is not having CMake > support a > show-stopper for you? I imagine adding support for it would be > straightforward. John, I now try to use

Dear All, I've developed a patch for mainline LLVM that integrates parts of the SAFECode memory safety compiler (http://sva.cs.illinois.edu) into LLVM. The patch includes transforms that add run-time safety checks to loads and stores and GetElementPtr instructions, a run-time library that implements the checks, a transform that enhances the run-time checks with source file debugging

John, The release source code (sc-main.tar) won't compile cleanly under Debian6-i386 (gcc/g++: 4.4.5). The compiler back trace is attached. Please fix it/them and repost. Or, 64b system is a requirement? Thank you Chuck llvm[4]: Compiling TypeRuntime.cpp for Release+Asserts build (PIC) cc1plus: warnings being treated as errors

Dear All, We now have two new mailing lists for SAFECode: 1) svadev: This mailing list is for discussion on SAFECode. Questions and comments about using SAFECode as well as development conversation on SAFECode can go here. 2) sva-commits: This mailing list gets email for all SVN commits made to SAFECode. -- John T.

Hi, My apologies for the trouble. I've disabled building DynamicTypeChecks for now (r138224) and now it builds cleanly on 32bit for me here. As for SAFECode support for 32bit vs 64bit, I believe 32bit should work just fine although I haven't personally tested this. Let me know if you have any further issues/questions. ~Will On Sun, Aug 21, 2011 at 9:26 AM, Chuck Zhao <czhao at

SVA/safecode looks interesting. Is it available to play with? I grepped for strings such as "sva" "secure" "safecode" in the LLVM source tree and didn't find anything, nor did I see obvious links to implementations from the project web pages. In the short term, questions I'd be interested in answering are: What happens when embedded codes that I care

Hello, Is the SVA codebase publically available, and if so, where can I find it? Thanks. -- gregory malecha -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110627/4f816aa6/attachment.html>

On 5/24/12 5:41 AM, Duncan Sands wrote: > 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 believe Nuno's goal is to prevent run-time exploitation of software. Nuno, please correct me if I'm wrong. And

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

How about state of SVA (Secure Virutal Archtecture)? It seems there is no any demo or prototype produced. Cheers, Liu Jian ---- email to: gjk.liu at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100420/e8dc1b16/attachment.html>

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

On Thu, May 24, 2012 at 9:23 PM, John Criswell <criswell at illinois.edu>wrote: > On 5/24/12 5:41 AM, Duncan Sands wrote: > > 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 :) > >

John Regehr wrote: > Qiuping, > > Have you looked at what has already been done? I would expect that taking > previous work such as this: > > http://llvm.org/pubs/2006-05-24-SAFECode-BoundsCheck.html > > and integrating into current LLVM would be a better idea than starting > over. > This code is publicly available from the SAFECode project (see

Thanks for the fast response John. On Thu, Oct 1, 2015, at 04:51 PM, John Criswell wrote: > Dear Ed, > > First, someone has updated the DSA code in the poolalloc project to LLVM > 3.7, and a Master's student worked for me over the summer to update a > large chunk of SAFECode to LLVM 3.7. However, the update to LLVM 3.7 > isn't finished (we need to finish integrating

Thank you all for the responses, John, My Bad here you go clang version 3.2 (trunk) Target: i386-pc-linux-gnu Thread model: posix [root at localhost opensrc]# cat /etc/centos-release CentOS release 6.2 (Final) Matthieu, Thanks for the fix and let me try again with latest trunk. ~Umesh On Mon, May 14, 2012 at 10:34 PM, Matthieu Monrocq <