search for: release_26

...tly trying to bootstrap llvm-gcc-4.2 from the latest stable LLVM release 2.6 on Solaris SPARC. The compilation with a self-build gcc-4.2.4 goes pretty well, however, I hit a seemingly widely know error during llvm-gcc's bootstrap in getting an assertion during the compile of /data/LLVM/src/GCC/RELEASE_26/gcc/libgcc2.c: /data/LLVM/src/GCC/RELEASE_26/gcc/libgcc2.c: In function '__powitf2': /data/LLVM/src/GCC/RELEASE_26/gcc/libgcc2.c:1765: internal compiler error: in HandleArgument, at llvm-abi.h:535 Looking into the code of llvm-abi.h, I added the following patch to it: --- /data/LLVM/src/...

...oders and LLVMers,<br /> > <br /> > There is some new work on moving DSA to the new LLVM 2.7 API. I am <br /> > hoping to do something similar for SAFECode once the code freeze occurs.<br /> > <br /> > To keep things running smoothly, there are now release_26 branches for <br /> > the poolalloc and safecode projects. If you are using SAFECode, <br /> > Poolalloc, or DSA with LLVM 2.6, you will want to switch to these branches.<br /> > <br /> > To get poolalloc and safecode out of these branches, use the following...

...c from the new branch. Begin forwarded message: > Dear SAFECoders and LLVMers, > > There is some new work on moving DSA to the new LLVM 2.7 API. I am > hoping to do something similar for SAFECode once the code freeze occurs. > > To keep things running smoothly, there are now release_26 branches for > the poolalloc and safecode projects. If you are using SAFECode, > Poolalloc, or DSA with LLVM 2.6, you will want to switch to these branches. > > To get poolalloc and safecode out of these branches, use the following > SVN commands: > > svn co http://llvm.o...

Hi, I'm interested in using the "Data Structure Analysis" that is apparently in the "poolalloc" module according to the documentation on alias analysis in LLVM. I have downloaded and built LLVM 2.6 on MinGW but the sources do not seem to include anything related to pool allocation. I don't think MinGW includes svn. Is there an download location where I can get the

Hello, Juergen > With the full patch, I get the assertion of the 'unhandled REAL_TYPE!', > so I wonder what needs to be done in order to get LLVM to produce > code for 'TREE_CODE(type) == REAL_TYPE' in the 'HandleArgument' function. > > > Does anyone have an idea? And why does this only happen on SPARC? What is the value of "Ty" in your case?

...you should be able to build mainline > DSA and Pool Allocation against it. > > If you have trouble building DSA/Pool Allocation, please email llvmdev. > To aid in checking out LLVM 2.6, I went and looked up the command. It is: svn co https://llvm.org/svn/llvm-project/llvm/branches/release_26 llvm -- John T.

Anton, I went with the first alternative with some success. However, now I get some errors during the build of libgcc with 'multiply defined symbols'. One thing I noticed is the following fact: Definition in unwind-pe.h: static const unsigned char * read_sleb128 (const unsigned char *p, _Unwind_Sword *val) --- GCC 4.2.4 bootstrapped on Solaris/SPARC -bash-3.00$ nm unwind-dw2.o | grep

Hello, Juergen > Ty->dump() prints "{double, double}" in the failing case (just before my > introduced assert). The answer is simple. The code in question contains extended IEEE FP argument / return type (aka 'long double'). By default it's lowered into struct {double, double} as you already saw and sparc currently does not provide any argument layout hooks. There

...ate] release_21 -> llvm.org/release_21 = [up to date] release_22 -> llvm.org/release_22 = [up to date] release_23 -> llvm.org/release_23 = [up to date] release_24 -> llvm.org/release_24 = [up to date] release_25 -> llvm.org/release_25 = [up to date] release_26 -> llvm.org/release_26 = [up to date] release_27 -> llvm.org/release_27 = [up to date] release_28 -> llvm.org/release_28 = [up to date] release_29 -> llvm.org/release_29 = [up to date] release_30 -> llvm.org/release_30 = [up to date] release_31 -> llv...

Hi Anton, thanks for the fast response. Ty->dump() prints "{double, double}" in the failing case (just before my introduced assert). HTH, and regards, Juergen On 10/30/09 16:19, Anton Korobeynikov wrote: > Hello, Juergen > >> With the full patch, I get the assertion of the 'unhandled REAL_TYPE!', >> so I wonder what needs to be done in order to get

...arded message: > > >> Dear SAFECoders and LLVMers, >> >> There is some new work on moving DSA to the new LLVM 2.7 API. I am >> hoping to do something similar for SAFECode once the code freeze occurs. >> >> To keep things running smoothly, there are now release_26 branches for >> the poolalloc and safecode projects. If you are using SAFECode, >> Poolalloc, or DSA with LLVM 2.6, you will want to switch to these branches. >> >> To get poolalloc and safecode out of these branches, use the following >> SVN commands: >> &gt...

...A and Pool Allocation against it. >> >> If you have trouble building DSA/Pool Allocation, please email llvmdev. >> >> > > To aid in checking out LLVM 2.6, I went and looked up the command. It is: > > svn co https://llvm.org/svn/llvm-project/llvm/branches/release_26 llvm > > -- John T. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > Does this mean poolalloc isn't meant to build with the...

...f several previous releases: $ git branch -r llvm-upstream/master llvm-upstream/release_1 llvm-upstream/release_16 llvm-upstream/release_20 llvm-upstream/release_21 llvm-upstream/release_22 llvm-upstream/release_23 llvm-upstream/release_24 llvm-upstream/release_25 llvm-upstream/release_26 llvm-upstream/release_27 llvm-upstream/release_28 llvm-upstream/release_29 llvm-upstream/svn-tags/RELEASE_1 llvm-upstream/svn-tags/RELEASE_20 llvm-upstream/svn-tags/RELEASE_21 llvm-upstream/svn-tags/RELEASE_22 llvm-upstream/svn-tags/RELEASE_23 llvm-upstream/svn-tags/RELEASE_24 l...

...; llvm.org/release_21 > = [up to date] release_22 -> llvm.org/release_22 > = [up to date] release_23 -> llvm.org/release_23 > = [up to date] release_24 -> llvm.org/release_24 > = [up to date] release_25 -> llvm.org/release_25 > = [up to date] release_26 -> llvm.org/release_26 > = [up to date] release_27 -> llvm.org/release_27 > = [up to date] release_28 -> llvm.org/release_28 > = [up to date] release_29 -> llvm.org/release_29 > = [up to date] release_30 -> llvm.org/release_30 > = [up to date]...

On 2011-08-29 04:21, Kurt Lidl wrote: > While I agree bootstrapping a new mirror from scratch is time and > resource consuming, this can be largely avoided by making a seed > of the svn tree available. (Basically, I think that looks like > a compressed tar file of the svn repository.) Or, a svnadmin dump > of the repo could be made available for the adventurous. Having the same

...hecker|cremebrulee|start|RELEASE_1.*|RELEASE_2[0-7])" Several problems here: 1. Bunch of additional branches / tags are created due to multiple branch points. I don't recall for llvm, but for clang we'll end with two tags per each release. Something like: $ git branch -r trunk tags/RELEASE_26 tags/RELEASE_26 at 84939 tags/RELEASE_27 tags/RELEASE_27 at 102415 tags/RELEASE_28 tags/RELEASE_28 at 115869 The problem will be much worse with new release branch scheme, basically we'll need to add each branch by hand, etc... 2. We really don't want to push arbitrary branches t...

Hi, I'm still using the release_26 version of Poolalloc/DSA with llvm 2.6 for my analyses and am currently trying to switch to llvm 2.7 for several reasons. I tried to use the trunk of the poolalloc svn repository with the llvm 2.7 release which is working fine for most of the programs I ran it on so far but for sqlite it's runn...

...created the 2.6 branch. As a reminder, please do not commit anything to the branch. If you have a patch that needs to be merged in, please email me directly with a link to the commit email. If you want to check it out, the branch is located here: https://llvm.org/svn/llvm-project/llvm/branches/release_26 https://llvm.org/svn/llvm-project/test-suite/branches/release_26 https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_26 Details for testing will come in the next day or so. Thanks, Tanya -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.ll...

Dear SAFECoders and LLVMers, There is some new work on moving DSA to the new LLVM 2.7 API. I am hoping to do something similar for SAFECode once the code freeze occurs. To keep things running smoothly, there are now release_26 branches for the poolalloc and safecode projects. If you are using SAFECode, Poolalloc, or DSA with LLVM 2.6, you will want to switch to these branches. To get poolalloc and safecode out of these branches, use the following SVN commands: svn co http://llvm.org/svn/llvm-project/poolalloc/branc...

I suggest you stick to John's release_26 branch of poolalloc for now. 2.7 breaks poolalloc, and dsa is undergoing some changes. Andrew On Tue, Mar 9, 2010 at 11:13 AM, John Criswell <criswell at uiuc.edu> wrote: > Dear Patrick and Antron, > > I've modified the Makefiles in the poolalloc module so that they do not >...