similar to: [LLVMdev] problems running test suite (-mllvm -disable-llvm-optzns)

Hi, > I'm trying to run some of the test suite using the instructions here: > > http://llvm.org/docs/TestingGuide.html#quicktestsuite > > I've built llvm myself, but I'm using pre-built binaries of llvm-gcc > (from http://llvm.org/prereleases/2.5/llvm-gcc4.2-2.5-x86-linux-RHEL4.tar.gz). > > Here's what happens: the llvm testsuite (from svn, right?) uses

Hi, > > I guess this is because the test suite is trying to run "llvm-gcc > > -mllvm -disable-llvm-optzns", which never seems to work, because > > llvm-gcc mangles the command line before it gets to cc1plus. > That's correct. The driver changes the order of the options provided. > You need to provided this option to cc1 / cc1plus directly Dan fixed this

Hello, Jay > I guess this is because the test suite is trying to run "llvm-gcc > -mllvm -disable-llvm-optzns", which never seems to work, because > llvm-gcc mangles the command line before it gets to cc1plus. That's correct. The driver changes the order of the options provided. You need to provided this option to cc1 / cc1plus directly > Is it just me having this

I've built a debug build of llvm 2.6, and llvm-gcc 2.6 for arm-elf with --enable-checking=yes. On the attached test case (which is g++.dg/expr/bitfield4.C from the GCC 4.2 testsuite) I get: $ cc1plus bitfield4.ii -emit-llvm-bc -o bitfield4.o -quiet cc1plus: /home/foad/svn/antix/toolchain/branches/w/foad/2757llvm26/toolchain/llvm/llvm-gcc/gcc/llvm-convert.cpp:999: llvm::Value*

GCC 3.x doesn't support -Wno-missing-field-initializers or -Wno-variadic-macros, so I get this build failure (with GCC 3.4.4 on Cygwin): make[3]: Entering directory `/home/foad/llvm/objdir-svn/utils/unittest/googletest' llvm[3]: Compiling gtest.cc for Debug build cc1plus: error: unrecognized command line option "-Wno-missing-field-initializers" cc1plus: error: unrecognized

Hi Zack, On Fri, Mar 13, 2009 at 4:41 PM, Zack Weinberg <zackw at panix.com> wrote: > I'm trying to persuade llvm (svn trunk) to build in a mode where it > *runs on* amd64 but *generates code* for alpha, exclusively.  (Well, > technically, generate code for my experimental architecture simulator > that happens to be based on alpha.)  I have been unable to find any >

On Fri, Mar 13, 2009 at 6:09 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Fri, Mar 13, 2009 at 4:41 PM, Zack Weinberg <zackw at panix.com> wrote: >> I'm trying to persuade llvm (svn trunk) to build in a mode where it >> *runs on* amd64 but *generates code* for alpha, exclusively. ... >>  - The "natural" way to do that (by which I mean

I'm trying to persuade llvm (svn trunk) to build in a mode where it *runs on* amd64 but *generates code* for alpha, exclusively. (Well, technically, generate code for my experimental architecture simulator that happens to be based on alpha.) I have been unable to find any combination of configure switches that makes this happen. I should probably underline that I am _not_ trying to

Hi, I got the following error message when I try to compile llvm-gcc with gcc 3.4.6: cc1plus: error: unrecognized command line option "-Wno-variadic-macros" make[3]: *** [llvm-main.o] Error 1 Someone have an idea ? thanks ________________________________ This message is confidential and intended only for the addressee. If you have received this message in error, please immediately

> To test clang: > 1) Compile llvm and clang from source. LLVM fails to build for me on Cygwin. I get: make[1]: Entering directory `/home/foad/llvm/objdir-2.6/runtime' make[2]: Entering directory `/home/foad/llvm/objdir-2.6/runtime/libprofile' llvm[2]: Compiling BasicBlockTracing.c for Release build (PIC) llvm[2]: Compiling BlockProfiling.c for Release build (PIC) llvm[2]:

On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> To test clang: >> 1) Compile llvm and clang from source. > > LLVM fails to build for me on Cygwin. I get: > Does TOT build? If not, please file a bug. Unfortunately Cygwin is not in our release criteria. I'd like to have a buildbot running (if there is not one already) and then get someone to qualify it for the

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: > >>> To test clang: >>> 1) Compile llvm and clang from source. >> >> LLVM fails to build for me on Cygwin. I get: >> > > Does TOT build? If not, please file a bug. No. Theres the runtime install bug (below), and llvm-gcc has a bug that I

On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > 2009/10/20 Tanya Lattner <lattner at apple.com>: >> >> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >> >>>> To test clang: >>>> 1) Compile llvm and clang from source. >>> >>> LLVM fails to build for me on Cygwin. I get: >>> >> >> Does TOT build? If not,

2009/10/20 Tanya Lattner <lattner at apple.com>: > > On Oct 20, 2009, at 12:05 PM, Aaron Gray wrote: > >> 2009/10/20 Tanya Lattner <lattner at apple.com>: >>> >>> On Oct 20, 2009, at 5:49 AM, Jay Foad wrote: >>> >>>>> To test clang: >>>>> 1) Compile llvm and clang from source. >>>> >>>> LLVM

On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote: > LLVMers, > > The 2.5 pre-release2 is finally available for testing: > http://llvm.org/prereleases/2.5/ > > If you have time, I'd appreciate anyone who can help test the release. > Please do the following: > > 1) Download/compile llvm source, and either compile llvm-gcc source or

Dear All, I'm getting the following error on Mac OS X when compiling C++ code in the LLVM test suite: g++ Output/minisat.llc.s -o Output/minisat.llc -lm -m64 -fomit-frame-pointer -mdynamic-no-pic -lstdc++ -lm Output/minisat.llc.s:5:Unknown pseudo-op: .cfi_startproc Output/minisat.llc.s:8:Unknown pseudo-op: .cfi_def_cfa_offset Output/minisat.llc.s:8:Rest of line ignored. 1st junk

I'm trying to cross-compile LLVM with build=, host=target=. I'm using the following packages from Debian lenny: mingw32 4.2.1.dfsg-1 mingw32-binutils 2.18.50-20080109-1 mingw32-runtime 3.13-1 The first problem I hit was when I configured with CC, CXX, AR and RANLIB set to mingw cross-tools, but forgot to specify NM as well. This resulted in a load of warnings that scrolled off the

On Sat, Feb 21, 2009 at 9:54 PM, Aaron Gray <aaronngray.lists at googlemail.com > wrote: > On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote: > >> LLVMers, >> >> The 2.5 pre-release2 is finally available for testing: >> http://llvm.org/prereleases/2.5/ >> >> If you have time, I'd appreciate anyone who can help

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,

Hello, I am new in using llvm so I would like to get some help on how to compile test-suite. Assumptions: llvm is in /llvm directory llvm-gcc is in /llvm-4.2-2.4-x86-linux-RHEL4/bin I have tried compiling test-suite and I get the following error: $make make[1]: Entering directory '/llvm/projects/test-suite/SingleSource' make[2]: Entering directory