similar to: Compiling SAFECode poolalloc in cygwin create different libraries compared to linux.

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 , This Is 'Suresh M' from AMD compiler team. 1) I obtained the source code of llvm and pool-alloc (relase_32 versions ) using the following commands, svn co http://llvm.org/svn/llvm-project/llvm/branches/release_32 llvm cd llvm/projects svn co http://llvm.org/svn/llvm-project/poolalloc/branches/release_32 poolalloc 2) Was able to build the binaries and libraries

Dear all, I'm a new user of LLVM. I'm trying to use DSA alias analysis in LLVM. I compiled llvm 3.0 and poolalloc (checkout from svn). I get the following lib in the ${poolalloc}/Release/lib/ : AssistDS.so libcount.so libpoolalloc_rt.so LLVMDataStructure.so poolalloc.so I tried to load all of them and do analysis by opt -load ${poolalloc}/Release/lib/<lib_name.so> -ds-aa

I updated the latest "poolalloc" code and the problem seems to have been fixed. However, I am still having problem of running "poolalloc". After compilation finished, there are several dynamic libraries created (libpoolalloc_rt.so, libpoolalloc_fl_rt.so and LLVMDataStructure.so). I was not sure which one I should use so I just tried all of them with "opt -load".

Haifeng He wrote: > I updated the latest "poolalloc" code and the problem seems to have been fixed. > However, I am still having problem of running "poolalloc". > > After compilation finished, there are several dynamic libraries > created (libpoolalloc_rt.so, libpoolalloc_fl_rt.so and > LLVMDataStructure.so). I was not sure which one I should use so I just

DSA should be current against head, but poolalloc isn't. I've changed DSA a bit so it may not compile with poolalloc as is. I haven't had time to tackle updating poolalloc (either to head or to the dsa changes). If you want the version from the paper, try checking out llvm 1.8 or 1.9 and a dsa from around then. The dsa as used on the linux kernel and in the OS work is in a branch

On 8/23/07, Wojciech Matyjewicz <wmatyjewicz at fastmail.fm> wrote: > Static ID fields in pass classes seem to be lacking definitions (there > were some changes in LLVM core classes and poolalloc hasn't been yet > fully updated to reflect them). The attached patch fixes this for DSA > classes - LLVMDataStructure.so loads into opt and DSA can be performed. Thanks. I forgot

Hi! Haifeng He wrote: > okay. I guess I figured it out. It seems "poolalloc" needs to be put > in llvm/projects/ directory. Yes, it will compile then. However, it seems the resulting shared library LLVMDataStructure.so (I haven't checked the others) has some undefined symbols. Trying to load it into the opt tool produces an error: undefined symbol:

Kostya, I think I've found what looks like a reproducible bug in libFuzzer. The code under test is built with ASan and the first ASan CHECK failure shows fuzzer in the stack trace. (see below) One of the factors that may be unique in my testing is that each iteration can take a very long time to execute (tens or hundreds of seconds). Let me know if you need more info, I think it

I'm continuing my quest to integrate _GLIBCXX_DEBUG into the config system. I now have things at a point where I can configure llvm to build with -D_GLIBCXX_DEBUG and the llvm-gcc will pick up the correct CPPFLAGS automatically. One thing I noticed in the llvm Makefile.rules is this: # If DISABLE_ASSERTIONS=1 is specified (make command line or configured), # then disable assertions by

First off, thanks -- this is a pretty great library and it feels like I'm learning a lot. I'm getting some more experience with libfuzzer and finding that I have a couple of questions: - How does libfuzzer decide to write a new test file? What distinguishes this one from all the other cases for which new test inputs were not written? Must be something about the path taken through the

Kostya, Here's the git repo: https://bitbucket.org/ebadf/fuzzpy I've only tested it on arm7 and x86_64 linux, I expect there's a good chance it may not work on other OSs. If you can build it successfully ("./build.sh", requires clang and clang++ in your path), then you should run the "testemail" case like so: while true; do ITERS=1000 ./run.sh

Ah, yes -- you need to clone with --recursive. I will try the workaround though. On Dec 3, 2015 1:12 PM, "Kostya Serebryany" <kcc at google.com> wrote: > > > On Wed, Dec 2, 2015 at 7:17 PM, Brian Cain <brian.cain at gmail.com> wrote: > >> Kostya, >> >> Here's the git repo: https://bitbucket.org/ebadf/fuzzpy >> >> I've only

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

On Tuesday 26 June 2007 14:05, Reid Spencer wrote: > I think you mis-interpreted something. That's not surprising. :) > If you build with -disable-assertions you are telling whatever build > mode (Debug or Release) to not include assertions. Consequently you get > either Release-Asserts (Release minus asserts) or Debug-Asserts (Debug > minus Asserts). I was wondering if

Hi David, On Mon, 2007-06-25 at 17:43 -0500, David A. Greene wrote: > I'm continuing my quest to integrate _GLIBCXX_DEBUG into the config system. > I now have things at a point where I can configure llvm to build with > -D_GLIBCXX_DEBUG and the llvm-gcc will pick up the correct CPPFLAGS > automatically. Okay. > > One thing I noticed in the llvm Makefile.rules is this:

Hello, git bisect helped me today in tracking down a regression in LLVM/Clang. Because LLVM/Clang code is split across multiple git repositories, there were a few obstacles to overcome prior to using git bisect. I thought I would share them here, in the hope that they're useful for others. The main difficulty was to check out the version of clang and compiler-rt that would compile with a

Mikhail Glushenkov wrote: > Hi Sanjiv, > > 2009/6/23 <Sanjiv.Gupta at microchip.com> > >>> BTW, Chris's Makefile changes broke llvmc yesterday (r75379). I'm >>> working on a fix. >>> >> Hi Mikhail, >> Did you get a chance to fix this. I still get errors while building examples. >> >> > > This issue

Hi all, I have a new sample project set up in my llvm/projects directory, and I'd eventually like my frontend to generate an LLVM IR tree. To do so, I believe I need to link to the appropriate LLVM libraries. That's where I'm stuck. I can't seem to find any specific documentation that describes how to set up a new project to link to LLVM libraries. To get started, I added a

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg