Patrick Alexander Simmons
2009-Jul-07 16:14 UTC
[LLVMdev] Stable release of pool allocation?
I've been attempting to write my pass (which depends on DSA and pool allocation) against the SVN trunk of LLVM and the llvm-poolalloc project. However, I was thinking it might be better to use the latest stable releases of these codebases. I know that this is the 2.5 branch for LLVM, but are there any stable releases of pool allocation? If so, would there be any disadvantage to my using it? --Patrick
poolalloc (and dsa for that matter) have never been stable. Both have always had known issues (and more once you try more interesting codes. You might try llvm 1.8 + llvm-gcc and poolalloc/dsa from that time, but I suspect you will have to backport fixes. Andrew On Tue, Jul 7, 2009 at 11:14 AM, Patrick Alexander Simmons<simmon12 at cs.uiuc.edu> wrote:> I've been attempting to write my pass (which depends on DSA and pool > allocation) against the SVN trunk of LLVM and the llvm-poolalloc > project. However, I was thinking it might be better to use the latest > stable releases of these codebases. I know that this is the 2.5 branch > for LLVM, but are there any stable releases of pool allocation? If so, > would there be any disadvantage to my using it? > > --Patrick > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Patrick Alexander Simmons wrote:> I've been attempting to write my pass (which depends on DSA and pool > allocation) against the SVN trunk of LLVM and the llvm-poolalloc > project. However, I was thinking it might be better to use the latest > stable releases of these codebases. I know that this is the 2.5 branch > for LLVM, but are there any stable releases of pool allocation? If so, > would there be any disadvantage to my using it? >There are currently no release branches of the automatic pool allocation project. This means that we don't know which revision of pool allocation was working at the time LLVM 2.5 was released. I and others keep the pool allocation project up-to-date with LLVM mainline, and we can help you diagnose problems with it, so mainline is your best bet, I think. Regarding the error that you saw, I tried running poolalloc on hello.bc on my Linux machine, and it did not assert or segfault. I'm hoping to update my Linux source to the latest poolalloc source code later today to make sure newer code isn't the problem (although I tend to doubt that this will change my results). I can also try poolalloc on Apoc to see if it does anything different than on the newer Linux machines. -- John T.> --Patrick > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Not sure if anybody has noticed: The PoolAlloc release source code extracted from SVN won't even build. I tried it last night, on WinXP/Cygwin, for both the LLVM-2.5 release, as well as the latest LLVM, neither would build -- with compile-time errors. With that being said, I have no idea which LLVM release the current PoolAlloc trunk is checked in with. Could anybody point this out? Or, at least make the least poolalloc build with either 2.5 or latest LLVM ? Thank you Chuck P.S. This is the command I used to extract PoolAlloc code: svn co http://llvm.org/svn/llvm-project/poolalloc/trunk poolalloc John Criswell wrote:> Patrick Alexander Simmons wrote: > >> I've been attempting to write my pass (which depends on DSA and pool >> allocation) against the SVN trunk of LLVM and the llvm-poolalloc >> project. However, I was thinking it might be better to use the latest >> stable releases of these codebases. I know that this is the 2.5 branch >> for LLVM, but are there any stable releases of pool allocation? If so, >> would there be any disadvantage to my using it? >> >> > There are currently no release branches of the automatic pool allocation > project. This means that we don't know which revision of pool > allocation was working at the time LLVM 2.5 was released. I and others > keep the pool allocation project up-to-date with LLVM mainline, and we > can help you diagnose problems with it, so mainline is your best bet, I > think. > > Regarding the error that you saw, I tried running poolalloc on hello.bc > on my Linux machine, and it did not assert or segfault. I'm hoping to > update my Linux source to the latest poolalloc source code later today > to make sure newer code isn't the problem (although I tend to doubt that > this will change my results). I can also try poolalloc on Apoc to see > if it does anything different than on the newer Linux machines. > > -- John T. > > >> --Patrick >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090707/fb6b188c/attachment.html>
Patrick Alexander Simmons wrote:> I've been attempting to write my pass (which depends on DSA and pool > allocation) against the SVN trunk of LLVM and the llvm-poolalloc > project. However, I was thinking it might be better to use the latest > stable releases of these codebases. I know that this is the 2.5 branch > for LLVM, but are there any stable releases of pool allocation? If so, > would there be any disadvantage to my using it? >I've tried the hello.bc file on both my machine and Apoc; it works on both. Can you update your LLVM and poolalloc trees and retry it? If it still doesn't work, can you send me your config.log and Makefile.common from your LLVM object tree? Thanks. -- John T.> --Patrick > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Patrick Alexander Simmons
2009-Jul-07 18:18 UTC
[LLVMdev] Stable release of pool allocation?
John Criswell wrote:> Patrick Alexander Simmons wrote: > >> I've been attempting to write my pass (which depends on DSA and pool >> allocation) against the SVN trunk of LLVM and the llvm-poolalloc >> project. However, I was thinking it might be better to use the latest >> stable releases of these codebases. I know that this is the 2.5 branch >> for LLVM, but are there any stable releases of pool allocation? If so, >> would there be any disadvantage to my using it? >> >> > There are currently no release branches of the automatic pool allocation > project. This means that we don't know which revision of pool > allocation was working at the time LLVM 2.5 was released. I and others > keep the pool allocation project up-to-date with LLVM mainline, and we > can help you diagnose problems with it, so mainline is your best bet, I > think. >Okay, thanks.> Regarding the error that you saw, I tried running poolalloc on hello.bc > on my Linux machine, and it did not assert or segfault. I'm hoping to > update my Linux source to the latest poolalloc source code later today > to make sure newer code isn't the problem (although I tend to doubt that > this will change my results). I can also try poolalloc on Apoc to see > if it does anything different than on the newer Linux machines. >The error only occurs for me using opt, in case I hadn't mentioned that.> -- John T. >--Patrick