similar to: [LLVMdev] [Fwd: Re: using dsa]

What versions of llvm and llvm-poolalloc should I check out of cvs, in order to use DSA? In a previous post John Criswell suggested checking llvm and llvm-poolalloc out of cvs using the -r release_19 flag. However, there were several post later that said that changes should not be made to the release_19 branch. At any rate, I've not seen any update on which versions of llvm and

I updated dsa to mainline cvs. Poolalloc is broken, however. On Mar 6, 2007, at 3:39 AM, Ryan M. Lefever wrote: > What versions of llvm and llvm-poolalloc should I check out of cvs, in > order to use DSA? In a previous post John Criswell suggested checking > llvm and llvm-poolalloc out of cvs using the -r release_19 flag. > However, there were several post later that said that

How do I acquire that version of DSA that you've updated to mainline cvs? Do I still check out llvm-poolalloc, or is there a way to only check out DSA? Patrick Meredith wrote: > I updated dsa to mainline cvs. Poolalloc is broken, however. > > On Mar 6, 2007, at 3:39 AM, Ryan M. Lefever wrote: > >> What versions of llvm and llvm-poolalloc should I check out of cvs, in

I have a few questions on using dsa now that it has been moved out of llvm. I have llvm -r release_19 checked out from cvs, and llvm-poolalloc -r release_19 checked out from cvs into the projects directory, as John Criswell previously suggested. 1) I have some compiler transforms that I'm writing that use DSA. They can no longer find the header files for DSA. My transforms are located

This kind of regression is a fallout of having some code live in separate CVS modules as "projects." It would help to have someone volunteer to maintain each project, which can be as little as making sure it continues to compile or as much as supporting it with answers to questions and bug fixes. Here is the current list of projects: llvm-poolalloc llvm-java (currently unused

Chris, I performed the steps you gave below to check out llvm-poolalloc. When I want to get new updates made to llvm-poolalloc, do I perform the following commands? cvs -d :pserver:anon at llvm.org:/var/cvs/llvm login <Hit return for an empty password> cd llvm/projects cvs -d :pserver:anon at llvm.org:/var/cvs/llvm update -r release_19 llvm-poolalloc In other words, do I specify the

Vikram S. Adve wrote: > This kind of regression is a fallout of having some code live in > separate CVS modules as "projects." It would help to have someone > volunteer to maintain each project, which can be as little as making > sure it continues to compile or as much as supporting it with answers > to questions and bug fixes. Here is the current list of projects:

Ryan M. Lefever wrote: > I have a few questions on using dsa now that it has been moved out of > llvm. I have llvm -r release_19 checked out from cvs, and > llvm-poolalloc -r release_19 checked out from cvs into the projects > directory, as John Criswell previously suggested. > > 1) I have some compiler transforms that I'm writing that use DSA. They > can no longer

> I recommend that you stick with the release_19 branch of both llvm and > llvm-poolalloc. I and others are actively using these branches, so > llvm-poolalloc bug fixes will most likely be made to this branch in > addition to mainline CVS for the forseeable future. The release_19 > branch of llvm-poolalloc is designed to always work with the release_19 > branch of LLVM, which

Tanya M. Lattner wrote: >>I recommend that you stick with the release_19 branch of both llvm and >>llvm-poolalloc. I and others are actively using these branches, so >>llvm-poolalloc bug fixes will most likely be made to this branch in >>addition to mainline CVS for the forseeable future. The release_19 >>branch of llvm-poolalloc is designed to always work with the

Thank you Patrick! For anyone interested, I was able to get the mainline version of DSA to compile with the mainline version of LLVM. As Patrick pointed out, the mainline version of PoolAllocate does not compile with the mainline version of LLVM. So, I made a small change to llvm-poolalloc/lib/Makefile in which I removed PoolAllocate from the line: PARALLEL_DIRS=DSA PoolAllocate After

Hi! I'm trying to run llvm-test (current CVS head) with the following command: $LLVMOBJDIR/projects/llvm-test$ make TEST=llc report I run into the following error: make[5]: Entering directory `$LLVMOBJDIR/projects/llvm-test/SingleSource/UnitTests/Vector/SSE' make[5]: *** No rule to make target `Output/sse.expandfft.linked.rbc', needed by `Output/sse.expandfft.linked.bc'. Stop.

[ 73%] Regenerating /Users/samuraicrow/Documents/workspace/llvm-trunk-build/tools/llvm-config/LibDeps.txt.tmp [ 73%] Updating /Users/samuraicrow/Documents/workspace/llvm-trunk-build/tools/llvm-config/LibDeps.txt if necessary... [ 73%] Checking for cyclic dependencies between LLVM libraries. find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMAsmPrinter.a

Dear all, I am trying to reproduce the "Percent May Alias" result described in PLDI 07's paper "Making Context-Sensitive Points-to Analysis with Heap Cloning Practical For The Real World" (http://llvm.org/pubs/2007-06-10-PLDI-DSA.html ). However, my "Percent May Alias" for all the benchmarks is much greater, especially "bzip2". The DSA code I use is

Dear All, We'd like to move the Data Structure Analysis (DSA) code from the LLVM source tree (lib/Analysis/DataStructure) into the Pool Allocation project. I plan on starting this move next week Tuesday. If this change somehow affects you and you need me to wait, please email me and let me know. Otherwise, I assume Tuesday is good. -- John T.

Dear John, I intend to implement the improvements on DSA. After running DSA on SPEC, I found DSA gives low precision for mcf and bzip2. I have checked the most imprecise c files in mcf an found that the code seems to be a mixture of "PHI" and "GEP" instructions. Could you please give me some hints about what the big picture of the improvement should be and how to start? Thank

On Tue, 13 Feb 2007, John T. Criswell wrote: >>> I recommend that you stick with the release_19 branch of both llvm and >>> llvm-poolalloc. I and others are actively using these branches, so >>> llvm-poolalloc bug fixes will most likely be made to this branch in >>> addition to mainline CVS for the forseeable future. The release_19 >>> branch of

$ make update ...snip... Updated to revision 69967. $ ENABLE_OPTIMIZED=1 make ...snip... llvm[1]: Regenerating LibDeps.txt.tmp llvm[1]: Checking for cyclic dependencies between LLVM libraries. find-cycles.pl: Circular dependency between *.a files: find-cycles.pl: libLLVMAsmPrinter.a libLLVMCodeGen.a libLLVMSelectionDAG.a llvm[1]: Building llvm-config script. cat:

On Fri, 8 Dec 2006, Ryan M. Lefever wrote: > I apologize if this has been answered previously, but why is DSA being > removed from LLVM? I ask because I am currently using the latest CVS > versions of LLVM and DSA. There are two reasons for doing this: 1. DSA is currently only used by llvm-poolalloc. 2. More seriously, DSA infringes on certain patents held by Microsoft, regarding

I apologize if this has been answered previously, but why is DSA being removed from LLVM? I ask because I am currently using the latest CVS versions of LLVM and DSA. Regards, Ryan John Criswell wrote: > Dear All, > > We'd like to move the Data Structure Analysis (DSA) code from the LLVM > source tree (lib/Analysis/DataStructure) into the Pool Allocation > project. I plan