similar to: [LLVMdev] installing llvm from source, make check-all fails on llvm::transforms and clang:preprocessor

Hi Simona, these failures are due to the name of the path to LLVM/clang, see below. > /scratch/user/download/release_30/build/Debug/bin/clang -cc1 -internal-isystem > /scratch/user/download/release_30/build/Debug/bin/../lib/clang/3.0/include > /scratch/user/download/release_30/llvm/tools/clang/test/Preprocessor/macro_paste_c_block_comment.c > > > -Eonly 2>&1 | not grep

I downloaded via svn the release_30 and current version code. I am on x86_64 GNU/Linux, I am compiling with gcc 4.4.6 I compiled release_30 with make ENABLE_OPTIMIZED=0 OPTIMIZE_OPTION=-O0 and current release with make In both cases, when I make check-all I get : FAIL: Clang :: Preprocessor/macro_paste_c_block_comment.c (2562 of 9598) ******************** TEST 'Clang ::

On 10/15/2011 05:02 AM, Bill Wendling wrote: > The LLVM 3.0 release branch has been tagged. You may now commit patches at your leisure. Could we have a release_30 branch in git tracking the SVN release_30 branch? Thanks, --Edwin

> Could we have a release_30 branch in git tracking the SVN release_30 branch? Added for {llvm,clang,compiler-rt,dragonegg}.git Let me know if I missed something :) -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Anton Korobeynikov <anton at korobeynikov.info> writes: >> Could we have a release_30 branch in git tracking the SVN release_30 branch? > Added for {llvm,clang,compiler-rt,dragonegg}.git Let me know if I > missed something :) Do we branch the test suite? Err...do we even have a test suite git mirror? -Dave

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]

I don't know about the LLVM errors, but I have seen the Clang error before. It occurs because the test is not path independent. In Preprocessor/macro_paste_c_block_comment.c you have 'nog grep scratch', which means that you can't have 'scratch' in your path. I think this should be reported as a bug. Regards, Patrik Hägglund -----Original Message----- From: llvmdev-bounces

I have now made a report at http://llvm.org/bugs/show_bug.cgi?id=11552. Patrik Hägglund -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Patrik Hägglund H Sent: den 13 december 2011 08:07 To: Brendan Kirby; Evan Cheng Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] make check-all failing 18 tests with --enable-optimized I

> 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

Thanks for this, I noticed this recently also (and internally expect it to fail). -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Patrik Hägglund H Sent: 13 December 2011 08:31 To: Brendan Kirby; Evan Cheng Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] make check-all failing 18 tests with --enable-optimized I have now made

On 12/12/11 19:29, Evan Cheng wrote: > On Dec 12, 2011, at 6:26 PM, Brendan Kirby wrote: > >> As part of our automated testing, I'm running make check-all to watch >> for failures. One of my builds uses the --enable-optimized option to >> configure. When I build the latest trunk, I'm now seeing 18 failing >> tests: >> Clang ::

Hi All , Was trying to build the LLVM src from http://llvm.org/svn/llvm-project/llvm/branches/release_30 ,But unable to build the same and clang poped up with below error . llvm[1]: Compiling IntervalMap.cpp for Debug build In file included from /root/projects/safecode/llvm/lib/Support/IntervalMap.cpp:14: /root/projects/safecode/llvm/include/llvm/ADT/IntervalMap.h:1980:32: error: use

As part of our automated testing, I'm running make check-all to watch for failures. One of my builds uses the --enable-optimized option to configure. When I build the latest trunk, I'm now seeing 18 failing tests: Clang :: Preprocessor/macro_paste_c_block_comment.c LLVM :: CodeGen/ARM/2011-05-04-MultipleLandingPadSuccs.ll LLVM :: CodeGen/ARM/2011-11-14-EarlyClobber.ll LLVM

Hi, I think there are a set of typos in the ATOMIC_LOAD_UMIN_I* and ATOMIC_LOAD_UMAX_I* pseudo-instructions . Specifically, def ATOMIC_LOAD_MIN_I32 : PseudoInst< (outs GPR:$dst), (ins GPR:$ptr, GPR:$val), NoItinerary, [(set GPR:$dst, (atomic_load_min_32 GPR:$ptr, GPR:$val))]>; and def ATOMIC_LOAD_UMIN_I32 : PseudoInst< (outs

On 11/13/12 12:37 PM, Chris Lattner wrote: > On Nov 13, 2012, at 7:52 AM, John Criswell <criswell at illinois.edu> wrote: > >>> John, it was not my intention to disrupt your work in any way. >>> However, branching for release is a bit of a grey area and I >>> have made a judgment call to branch SAFECode in sync with llvm. >>> This could have been a

On 12/13/11 01:09, Eli Friedman wrote: > On Mon, Dec 12, 2011 at 6:26 PM, Brendan Kirby <bkirby at mips.com> wrote: >> As part of our automated testing, I'm running make check-all to watch >> for failures. One of my builds uses the --enable-optimized option to >> configure. When I build the latest trunk, I'm now seeing 18 failing >> tests: >>

Hi All, I am working on a bug in clang. I already have a fix for it and I am going through the "LLVM Testing Infrastructure Guide" to make sure I haven't broken anything else. I have few questions regarding the test suite infrastructure that I hope someone can answer. 1. I checked out and built llvm, clang, and test-suite from svn tip. When I run llvm/test *without* my changes on

On Mon, Dec 12, 2011 at 6:26 PM, Brendan Kirby <bkirby at mips.com> wrote: > As part of our automated testing, I'm running make check-all to watch > for failures.  One of my builds uses the --enable-optimized option to > configure. When I build the latest trunk, I'm now seeing 18 failing > tests: >    Clang :: Preprocessor/macro_paste_c_block_comment.c >    LLVM ::

On Mon, Sep 5, 2016 at 3:20 AM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > On Sun, Sep 4, 2016 at 1:06 PM, Simona Simona via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hello, >> >> I'm trying to add a new instruction after a given instruction in a basic >> block. >> Until LLVM 3.7, I was using the following code:

Why not just use Instruction::insertAfter()? I->insertAfter(new_inst); On Mon, Sep 5, 2016 at 8:13 AM, Ryan Taylor via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Try incrementing the iterator before using. > > On Sep 5, 2016 10:26, "Simona Simona via llvm-dev" < > llvm-dev at lists.llvm.org> wrote: > >> On Mon, Sep 5, 2016 at 3:20 AM, Daniel