search for: safecode

Hi John, That worked for me. I am using llvm 3.2 only and following http://safecode.cs.illinois.edu/docs/Install.html So for I am able to make inside llvm/projects/poolalloc by doing such cosmetic changes. Now, when I tried to make inside llvm/projects/safecode, I see another error. kpawar at KPAWAR-LT ~/SAFECode/LLVM_SRC/llvm/projects/safecode $ /usr/bin/clang -cc1 -triple i386...

...e+Asserts/lib/LLVMDataStructure.a ./Release+Asserts/lib/poolalloc.a ./Release+Asserts/lib/AssistDS.a ./Release+Asserts/lib/libpoolalloc_fl_rt.a ./Release+Asserts/lib/libpoolalloc_rt.a ./Release+Asserts/lib/libpa_pre_rt.a ./Release+Asserts/lib/libcount.a On cygwin I observed kpawar at KPAWAR-LT ~/SAFECode/LLVM_SRC/llvm/projects/poolalloc $ find . -name *.a ./Release+Asserts/lib/libAssistDS.a ./Release+Asserts/lib/libcount.a ./Release+Asserts/lib/libLLVMDataStructure.a ./Release+Asserts/lib/libpa_pre_rt.a ./Release+Asserts/lib/libpoolalloc.a ./Release+Asserts/lib/libpoolalloc_fl_rt.a ./Release+Assert...

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...

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 eecg.toronto.edu> wrote: > John, > > The release sourc...

...an6-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 /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:52: error: integer constant is too large for ‘long’ type /home/czhao/ResearchTools/LLVM/SubProjects/Safecode/llvm/projects/poolalloc/runtime/DynamicTypeChecks/TypeRuntime.cpp:99: error: integer constant is too large for ‘long...

Hello All, I am looking at exploring what benefits SAFECode has to offer over clang S.A and llvm's instrumentation tools like memory sanitizer and address sanitizer. I could come up with the following that are not provided in ASAN/MSAN/Clang S.A -> dangling pointer error and detection -> crashes in system libraries due to security vulnerabilities...

On 2/26/15 9:54 AM, Jyoti Rajendra Allur wrote: > Hello All, > I am looking at exploring what benefits SAFECode has to offer over clang S.A and llvm's instrumentation tools like memory sanitizer and address sanitizer. Are you looking for an off-the-shelf tool, or are you looking for approaches to use in your own tool? > I could come up with the following that are not provided in ASAN/MSAN/Clang S.A...

...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 contributions to SAFECode as of yet, I'd like to follow the same policy that LLVM uses (notably that the copyright of contributions is passed to the University of Illinois). Is this acceptable to you? We haven't regularly tested SAFECode and Automatic Pool Allocation on 64 bit architectures, so while it may wo...

...rote: > On Nov 13, 2012, at 7:52 AM, John Criswell <criswell at illinois.edu> wrote: > >>> John, it was not my intention to disrupt your work in any way. >>> However, branching for release is a bit of a grey area and I >>> have made a judgment call to branch SAFECode in sync with llvm. >>> This could have been a bit overzealous but I am used to >>> "release at any time" approach or agile project management. >>> >>> Since LLVM/Clang has grown so much I think the release process >>> will require some adjust...

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 Comm...

Please create a similar branch for Klee; I've been working on porting that to 2.7 as well.<br /> <br /> Best, Erich Ocean<br /> <br /> On Fri, Mar 5, 2010 at 8:43 PM, John Criswell (criswell@uiuc.edu) wrote:<br /> > <br /> > Dear SAFECoders and LLVMers,<br /> > <br /> > There is some new work on moving DSA to the new LLVM 2.7 API. I am <br /> > hoping to do something similar for SAFECode once the code freeze occurs.<br /> > <br /> > To keep things running smoothly, there are now rel...

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: http://soc...

I’ve been debugging SAFECode source code files, and line 170 in ArrayBoundCheckLocal.cpp has been causing the following compilation error: In file included from /Users/peterfinn/Desktop/llvm_trunk_2/projects/safecode/lib/ArrayBoundChecks/ArrayBoundCheckLocal.cpp:18: In file included from /Users/peterfinn/Desktop/build/project...

Hello, I have tried a lot fix this error but am not able to can you please find me a solution am trying to compile the SAFECode in Cygwin Environment to work for windows. used make -j4 command to make the files in cygwin i have got this error make[5]: Leaving directory '/home/uidr7475/Work/LLVM_OBJ/projects/safecode/tools/clang/include' /usr/bin/cp: cannot stat '/home/uidr7475/Work/LLVM_SRC/projects/safecod...

Dear LLVMers, We are happy to announce an alpha release of the SAFECode compiler. It is now available for download from the LLVM public Subversion repository. SAFECode uses a set of analysis passes and program transformations to provide strong memory safety guarantees to C/C++ programs. Specifically, the safety guarantees are: o Array bounds checking (prevents...

...een release managers. :) In the past, I recall the release manager made branches of LLVM, Clang, and test-suite because all 3 of those projects followed LLVM mainline. Other projects simply followed whatever branching policy they wanted. > >> Pawel, you created a release_32 branch of SAFECode last night without my >> consultation. That commit itself is fine since we just happen to be >> tracking LLVM mainline right now; I'll just tell SAFECode developers to >> move development to the release_32 branch. However, in general, you >> can't assume that SAFECo...

...gt; 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 just recognizes certain >> functions as >> allocators and knows how to interpret the arguments to find the size. >> If we want >> SAFECode to work with another allocator (like a program's custom >> allocator, the >> Objective-C allocator,...

...3:51 AM, Duncan Sands wrote: > 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! 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 argumen...

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 All , Was trying to build the LLVM src from http://llvm.org/svn/llvm-project/llvm/branches/release_30 ,But unable to build the same and clang poped up with below error . llvm[1]: Compiling IntervalMap.cpp for Debug build In file included from /root/projects/safecode/llvm/lib/Support/IntervalMap.cpp:14: /root/projects/safecode/llvm/include/llvm/ADT/IntervalMap.h:1980:32: error: use 'template' keyword to treat 'newNode' as a dependent template name Node[NewNode] = this->map->newNode<NodeT>(); ^...