<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=gb18030" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Not sure if anybody has noticed:<br>
<br>
The PoolAlloc release source code extracted from SVN won't even build.<br>
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.<br>
<br>
With that being said, I have no idea which LLVM release the current
PoolAlloc trunk is checked in with.<br>
Could anybody point this out?<br>
Or, at least make the least poolalloc build with either 2.5 or latest
LLVM ?<br>
<br>
Thank you<br>
<br>
Chuck<br>
<br>
P.S.<br>
This is the command I used to extract PoolAlloc code:<br>
svn co <a class="moz-txt-link-freetext" href="http://llvm.org/svn/llvm-project/poolalloc/trunk">http://llvm.org/svn/llvm-project/poolalloc/trunk</a> poolalloc<br>
<br>
<br>
John Criswell wrote:
<blockquote cite="mid:4A537E24.7010107@cs.uiuc.edu" type="cite">
<pre wrap="">Patrick Alexander Simmons wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap=""><!---->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.
</pre>
<blockquote type="cite">
<pre wrap="">--Patrick
_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a class="moz-txt-link-freetext" href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>
<a class="moz-txt-link-freetext" href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a>
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
LLVM Developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:LLVMdev@cs.uiuc.edu">LLVMdev@cs.uiuc.edu</a> <a class="moz-txt-link-freetext" href="http://llvm.cs.uiuc.edu">http://llvm.cs.uiuc.edu</a>
<a class="moz-txt-link-freetext" href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a>
</pre>
</blockquote>
<br>
</body>
</html>