similar to: [LLVMdev] LLVMdev Digest, Vol 87, Issue 17

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.

Are there any plans to add CMake support to the build of SAFECode? Also are there any current instructions for building llvm/clang with SAFECode support from current svn? Jack

Hello, I’m trying to get the SAFECode compiler up and running for work I’ll be doing, and in trying to configure LLVM (according to the information at http://llvm.org/docs/GettingStarted.html), I ran into some confusion. In step 8 in the section "Getting Started Quickly (A Summary)”, I realized that I wouldn’t be able to follow the steps exactly as described, because they tell me to create

On 6/18/15 6:49 PM, Eric Christopher wrote: > Hi John, > > Long term we don't want to keep the burden of two build systems in > tree. CMake is turning out to be the build system we want because of > its multi-platform support, etc and as soon as the CMake system can do > everything we can do with the autoconf/makefile build I plan on > turning down the support for that

----- Original Message ----- > From: "Eric Christopher" <echristo at gmail.com> > To: "John Criswell" <jtcriswel at gmail.com>, LLVMdev at cs.uiuc.edu, "Chris Bieneman" <beanz at apple.com> > Sent: Thursday, June 18, 2015 7:14:06 PM > Subject: Re: [LLVMdev] Long-Term Support for LLVM Projects Extension to Build System? > > > On

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

On 11/24/16 3:12 AM, Arnaud De Grandmaison via llvm-dev wrote: > > Hi Sandeep, > > The CMake version of the test-suite has been improved (see > https://reviews.llvm.org/D21360) so that it’s easy to plug additional > test suites. A starting point would be to look at how the > TEST_SUITE_SUBDIRS variable in the top level CMakeLists.txt is used. > I think this bug report

Daniel, Kostya, We had a meeting with the Clang people (Chris, Doug, Ted) on Thursday before the llvmdev meeting about adding dynamic checking tools into Clang -- IOC for undefined integer behaviors, and SAFECode for memory safety. SAFECode has similar goals to AddressSanitizer, though at least for now it has more checks, but is slower. The main conclusion was that we should have a common

I hope this is the correct avenue to contact the poolalloc developers. I'm trying to use an alias analysis from the poolalloc repository and can't get it to compile with the latest LLVM. CMake is now required for LLVM, I'm pretty sure at least, but poolalloc does not seem to use it correctly. The README in the project refers to the old Makefiles. I corrected a minor CMake error and a

Dear All, Will the LLVM project system (the extension to the build system that allows sub-projects to reuse the LLVM Makefiles) be maintained long term, or is the slow push to CMake intending to deprecate this functionality? We used this feature a lot for research projects at UIUC, but if the current maintainers of the build system are planning on deprecating it, I'll have my students

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

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

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

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

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

On 11/13/12 12:37 PM, Chris Lattner wrote: > 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

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

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

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.

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 just recognizes certain functions as > allocators and knows how to interpret the arguments