similar to: [LLVMdev] SVN GIT version corresponding to release

Won't it be http://llvm.org/svn/llvm-project/llvm/tags/RELEASE_31/final/ On Tue, Jan 8, 2013 at 7:46 PM, Pankaj Gode <godepankaj at yahoo.com> wrote: > Hi All, > > I was checking for GIT or SVN versions corresponding to llvm3.1 release by > checking svn and git logs, but failed to find the exact match. > > I checked with r156747, which is the last version it shows

I always though the /tags/RELEASE_xx/final branch would hold the final, released tarball contents, but this does not appear to be the case, at least not for 3.1. I can confirm that diffing /tags/RELEASE_31/final and the 3.1 tarball shows some non-trivial changes. The 3.2 release seems to be okay though; the diff only shows changes in the last-modified timestamps in the HTML docs. Though I just

Hi Anton, git-svn got confused at the branch point for the release_31: I see that the current release_31 branch has been created on r155051 as a copy of r155050 from trunk, and r155050 is actually removing an older release_31 branch: Revision 155050 Author: void Date: Wed Apr 18 16:38:33 2012 CDT (11 days, 20 hours ago) Log Message: Removing old release_31 branch for rebranching. This

FYI, I have been maintaining my own release_31 manually on github.com/chapuni. 2012/5/1 Sebastian Pop <spop at codeaurora.org>: > Hi Anton, > > git-svn got confused at the branch point for the release_31: I see > that the current release_31 branch has been created on r155051 as a > copy of r155050 from trunk, and r155050 is actually removing an older > release_31 branch:

> In your svn section of llvm/.git/config, you can specify how to map > the svn branches to different name spaces, something like this: > > [svn-remote "svn"] >        [...] >        branches = branches/*:refs/remotes/origin/* >        fetch = branches:refs/remotes/origin > > I would also change "branches = branches/*:refs/remotes/origin/*" > into

Hi Anton, On Thu, Apr 26, 2012 at 4:05 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Sebastian, > >> I just saw that the git branch remotes/origin/release_31 has been created >> for llvm.  Unfortunately it is missing the right context: right now I can only >> see 11 patches in that branch with the last patch having no parent. >> >> Could

On Sun, May 6, 2012 at 10:20 AM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > FYI, I have been maintaining my own release_31 manually on github.com/chapuni. > Thanks for the pointer. I was waiting for Anton to fix the llvm.org git repo for the 3.1 branch. Anton, could you please try to fix the release_31 git branch? Thanks, Sebastian > 2012/5/1 Sebastian Pop <spop at

What do you mean by "current top of tree"?   Pankaj ________________________________ From: Eric Christopher <echristo at apple.com> To: Pankaj Gode <godepankaj at yahoo.com> Cc: "llvmdev at cs.uiuc.edu" <llvmdev at cs.uiuc.edu> Sent: Monday, October 3, 2011 10:32 PM Subject: Re: [LLVMdev] collect end line number for scope On Oct 3, 2011, at 4:36 AM,

Hi Team, I am migrating one of the Pass that was written for llvm2.2 or older to llvm3.1. The code snippet looks like the following: Constant *func; void add( Module *M) { func = M->getOrInsertFunction("func", Type::getVoidTy(M->getContext()), NULL); } virtual bool runOnModule(Module &M) { add (&M); for(Module::iterator F = M.begin(), E = M.end(); F !=

Hi Guys, I am using the Postdom pass and I would like to get the root of the tree. However, everytime I try to get the root, I get a segfault. I don't know why the environment can't find DominatorTreeBase. Below is the code that generates the Segfault. In my .h file I include Dominators.h PDT.getRootNode(); //PDT is a reference to a PostDominatorTree dyld: lazy symbol binding

Hi Ahmad, On 03/01/13 16:26, Hassan, Ahmad wrote: > Hi Team, > > I am migrating one of the Pass that was written for llvm2.2 or older to llvm3.1. > The code snippet looks like the following: > > Constant *func; > > void add( Module *M) { > > func = M->getOrInsertFunction("func", Type::getVoidTy(M->getContext()), NULL); this function has no

Hi, He is referring to current SVN head. Regards, Alex On Tue, Oct 4, 2011 at 12:08 PM, Pankaj Gode <godepankaj at yahoo.com> wrote: > What do you mean by "current top of tree"? > > Pankaj > From: Eric Christopher <echristo at apple.com> > To: Pankaj Gode <godepankaj at yahoo.com> > Cc: "llvmdev at cs.uiuc.edu" <llvmdev at

Hello, Is there any package to install llvm 3.1 on solaris?  Standard installation by compiling the sources does not run smoothly. I found that similar issues have been addressed before, but without replies: http://clang-developers.42468.n3.nabble.com/Using-Clang-LLVM-on-sparc-solaris-td2807126.html I tried to install llvm 3.1 on a system with Sun Microsystems Inc.   SunOS 5.10      Generic

Hi Eric,   Thanks for patch information. I have checked the patch with my code and I see that it works. But when I extract the variable and check the metadata information to retrieve the scope information, I do not get exact scope, after optimization. As you said that this is a work in progress, so can we expect full version on this in llvm3.3 release ?   Regards, Pankaj  

That is what I don't understand. This symbol is defined in Dominators.h, which I include in my file. I don't understand why I am getting this error. Here is my opt command, "opt -load LLVMMyDomPass.dylib -mdp < test.bc > test.d.bc" George On Tue, Aug 21, 2012 at 3:25 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi George, > > ... > > dyld: lazy

Hi All,   Due to 'LowerDbgDeclare' call ( as part of 'instruction combining' optimization), a local variable gets declared and initialized inside the basic blocks it is used in. Is there anyway I can avoid this ?   This is with reference with my previous question. http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061644.html     Regards, Pankaj -------------- next part

Hi,   The link and the information shared was helpful.   I will make my problem definition more clear. While I am "asm printing" target code, I also want to emit scope related information. Scope related information includes, - for each scope, start line, end line, start column, end column and - scope heirarchy. As scope is delimited by "{" and "}" (for an input

There was a patch committed the other day that should, at least, work around some of the behavior you describe. Optimized debug info is an area that's being worked on in ToT and previous releases are particularly bad. I'd use that. -eric On Mon, Apr 29, 2013 at 7:02 AM, Pankaj Gode <godepankaj at yahoo.com> wrote: > Hi All, > > Due to 'LowerDbgDeclare' call ( as

I.e., I see this when I run `git fetch`: ``` $ git fetch -v llvm.org From http://llvm.org/git/llvm = [up to date] master -> llvm.org/master = [up to date] release_1 -> llvm.org/release_1 = [up to date] release_16 -> llvm.org/release_16 = [up to date] release_20 -> llvm.org/release_20 = [up to date] release_21 -> llvm.org/release_21 = [up to date]

Hi All,   int global; int func( int t) {    //scope 1   {      ....   } <-----   return x; }   For the above code, i want to collect endline (indicated by <---) for the scope. Can we get this information from the Dwarf Information in llvm 2.9 ?     Thanks & Regards, Pankaj -------------- next part -------------- An HTML attachment was scrubbed... URL: