similar to: [LLVMdev] Buildbot

No, some build release, and some build release-asserts. Historically, this is a typical sign of llvm being miscompiled, see the broken-gcc list. - Daniel On Mon, Feb 15, 2010 at 10:09 AM, David Greene <dag at cray.com> wrote: > Do the buildbots only build debug components?  I am seeing lots of this on > trunk with release-style builds: > > [x86_64-off-opt]: Failed with

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]

Oliver Schneider <gmane at assarbad.net> writes: >>> However, we have official git mirrors of most of the projects on >>> llvm.org, would using them instead of svnsync be an option for you? >> >> Well, if the authoritative source code control system for all the >> llvm projects is svn, I'd just as soon use svn as the tool at my end. > The git

> On 2016-Feb-05, at 15:22, James Y Knight <jyknight at google.com> wrote: > > That usually happens when someone deletes and then recreates an svn branch with the same name, as happened in r215001 and r215011. > It can be deleted now, if anyone wants to. ``` $ git push llvm.org :release_35 at 215010 fatal: unable to access 'http://llvm.org/git/llvm.git/': The requested

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

Hey, I have written a few lines about Release and Debug Builds (SVN checkout vs. LLVM distribution). I've also added the RELEASE_25 tag to the tags list and corrected a typo. Can someone please review? As I'm not a native speaker/writer it may contain strange wording/spelling mistakes ;). Any feedback welcome. BR Josef -- zapster -------------- next part -------------- A non-text

Maurice Gittens wrote: > Hi all, > > I just svn-updated the 2.5 branch on my machine and I noticed this > warning during the build. > > *** Warning: Linking the shared library > /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool > *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o >

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 Wed, Aug 17, 2011 at 01:47:02PM -0700, Benjamin Kramer wrote: > On 17.08.2011, at 11:36, Kurt Lidl <lidl at pix.net> wrote: > > > Why can't I mirror the whole tree? > > The original reason for this limitation was that complete checkouts > put a lot of stress on the server. While I agree bootstrapping a new mirror from scratch is time and resource consuming,

Hi all, I just svn-updated the 2.5 branch on my machine and I noticed this warning during the build. *** Warning: Linking the shared library /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool *** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o /home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o

LLVMers, The 2.5 release branch has been created. You may check it out with the following commands: svn co https://llvm.org/svn/llvm-project/llvm/branches/release_25 svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_25 svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_25 Please do not commit anything to the release branch. If you have a patch that needs

LLVMers, The 2.5 release branch has been created. You may check it out with the following commands: svn co https://llvm.org/svn/llvm-project/llvm/branches/release_25 svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_25 svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_25 Please do not commit anything to the release branch. If you have a patch that needs

> 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 all, I have a question regarding populating ValueSymbolTable of a Function. Is it that ValueSymbolTable is populated automatically whenever an alloca instruction is created using IRBuilder or do we need to explicitly populate?? If we need to populate explicitly, the insert method in ValueSymbolTable is private, so how can we do it? Currently, I am trying to access the symbol table as below:

A simulator should be expecting the machine opcodes not macros. LD shouldn't care at all as long as the object format plays well. I would think it would be better to fix the simulator. Jack ________________________________________ From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] on behalf of llvmdev-request at cs.uiuc.edu [llvmdev-request at cs.uiuc.edu] Sent: Thursday,

subramanyam wrote: > > Hi all, > I have a question regarding populating ValueSymbolTable of a Function. > Is it that ValueSymbolTable is populated automatically whenever an alloca > instruction is created using IRBuilder or do we need to explicitly > populate?? It's maintained by LLVM for you, by Value::setName and other methods. Nick

Nick Lewycky wrote: > > > > It's maintained by LLVM for you, by Value::setName and other methods. > > Nick > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > I am getting the following error when trying to

> I am getting the following error when trying to fetch the symbol table using > getValueSymbolTable() Why do you want to do this? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Anton Korobeynikov-2 wrote: > >> I am getting the following error when trying to fetch the symbol table >> using >> getValueSymbolTable() > Why do you want to do this? > > > > I want to access some of the variables created in the function. -- View this message in context: http://old.nabble.com/Using-ValueSymbolTable...-tp29461430p29469794.html Sent from

Hello, I'm using llvm 2.5. I initially built it with GCC 4.1.2 and it completed building. But when I run it with a simple test function, it fails with the following issue: Value still in symbol table! Type = 'i32' Name = 'a' Value still in symbol table! Type = 'i32' Name = 'b' llc: ValueSymbolTable.cpp:29: llvm::ValueSymbolTable::~ValueSymbolTable():