[LLVMdev] Stable release of pool allocation?

[Mai, Haohui]

Pool allocation tries to match up with trunk LLVM in order to get bug  
fixes and experimental features from LLVM.

There's no guarantee that Pool Allocation will build on trunk since  
the APIs of LLVM are changing every day. And that's the most common  
reason why a nightly build of Pool Allocation fails I have seen so far.

As far as I know, pool allocation works pretty well on Linux and Mac  
OS X. The maintainers of pool allocation pay no efforts, and currently  
have no plans to build / test pool allocation on windows platform.  
That might be another reason why your attempt to build is failed.

It would be appreciated if you could sit down, figure why the build  
fails and submit a patch to llvm-dev. These patches are always welcomed.

Haohui

On Jul 7, 2009, at 12:26 PM, Chuck Zhao wrote:

> 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
>>
>
> _______________________________________________
> 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/20090708/b876d263/attachment.html>