search for: llvmgxx

...inactive builder and want to reactivate it. 4. There are RSS and Atom feeds for failures are http://google1.osuosl.org:8011/rss and http://google1.osuosl.org:8011/atom. 5. All builders except MSVC are now running the unittests. 6. Configure style builders now use --without-llvmgcc and --without-llvmgxx to avoid problems with failing Frontend tests. In the longer term we should add builders which build llvmgcc and do not have this problem. Please let me know if you have questions, problems, or suggestions. For those interested in how it is setup, most of the configuration stuff is now checked in...

Hi, I built LLVM + Clang on Mac OS X and ran make check. I get the following result summary: Failing Tests (11): LLVM :: LLVMC/C++/dash-x.cpp LLVM :: LLVMC/C++/hello.cpp LLVM :: LLVMC/C++/just-compile.cpp LLVM :: LLVMC/C++/together.cpp LLVM :: LLVMC/C++/unknown_suffix.unk LLVM :: LLVMC/C/hello.c LLVM :: LLVMC/C/opt-test.c LLVM :: LLVMC/C/sink.c LLVM ::

....def:27: error: ‘void LLVMInitializeX86TargetAsmPrinter()’ previously defined here make[3]: *** [/llvm/stage1/lib/MC/MCDisassembler/Release/EDDisassembler.o] Error 1 ==== config Darwin10 x86_64 (and llvm-gcc from Xcode 3.2.3). ../configure --prefix=/opt/llvm-selfhost --without-llvmgcc --without-llvmgxx --disable-bindings --disable-assertions --enable-optimized --enable-targets=x86,x86_64 CC=llvm-gcc CXX=llvm-g++ === Is somebody else having trouble with this change ? -- Jean-Daniel

...it is also needed on some platforms so that llvm-nm can be found in the path when the CFE is configuring the libstdc++ (don't ask why!). Quick Fix: 1. Put the $CFEINSTALL/bin directory into your PATH variable 2. Remove $CFEINSTALL/bin/* 3. Remove shell aliases for "llvmgcc" and "llvmgxx" or change them to invoke llvm-gcc and llvm-gxx. 4. Rebuild llvm with "make tools-only" 5. Rebuild the CFE with --program-prefix=llvm- 6. Rebuild llvm with "make" More Details: 1. Put the $CFEINSTALL/bin directory into your PATH variable. We're going to confi...

On Tuesday 21 July 2009 12:01, Daniel Dunbar wrote: > 6. Configure style builders now use --without-llvmgcc and > --without-llvmgxx to avoid problems with failing Frontend tests. In > the longer term we should add builders which build llvmgcc and do not > have this problem. I have a builder that does this today. When are you checking your stuff into the LLVM repository? I'd like to graft my stuff onto that....

On 08/05/2010 07:54 PM, Daniel Dunbar wrote: > Hi Argyrios, > > This has been happening for a long time, no one has debugged it yet. > > I personally always configure llvm with --without-llvmgcc and > --without-llvmgxx, which disables these tests. I believe the reason is that llvmc is not built at all with the cmake system. Here is the relevant bug report. http://llvm.org/bugs/show_bug.cgi?id=5648 Tobias

...at 10:17 AM, Garrison Venn wrote: > Ok thanks I'll try that. I was trying to avoid re-building llvm-gcc. You don't need llvm-gcc to run most of the "make check" tests. The FrontEnd tests use it, but that's all. If you run configure with "--without-llvmgcc --without-llvmgxx", then it shouldn't use llvm-gcc at all. > > Garrison > > On Dec 10, 2010, at 12:12, Bob Wilson wrote: > >> >> On Dec 10, 2010, at 6:11 AM, Garrison Venn wrote: >> >>> Hey Chris, >>> >>> Ok, so I'm working on creating t...

Hi All, Is it possible to run the test-suite with another compiler that it's not llvm-gcc? I want to run tests with Clang and our bridge+LLVM. Also, llvm-gcc is going to be deprecated soon enough, would be good to have the official way to use Clang. Or is this doc too old to reflect the current status? http://llvm.org/docs/TestingGuide.html cheers, --renato

On Jun 30, 2011, at 5:20 AM, Renato Golin wrote: > Hi All, > > Is it possible to run the test-suite with another compiler that it's > not llvm-gcc? I use --with-built-clang --with-llvmcc=clang --with-llvmcxx=clang++ --without-llvmgcc --without-llvmgxx on llvm configure line to use clang built within tree. I checkout clang sources inside my llvm/tools folder. - Devang > > I want to run tests with Clang and our bridge+LLVM. > > Also, llvm-gcc is going to be deprecated soon enough, would be good to > have the official way to use...

...>  Unexpected Failures: 11 > > I see the error : > > llc: <temp-filename>.bc: Unknown instruction for all the tests. > > Are these failures known/expected? If not, am I doing something wrong? Known/expected. You can work around it by passing --without-llvm-gcc --without-llvmgxx to configure. IIRC, Eric will be fixing the tests soon. -Eli

Ok thanks I'll try that. I was trying to avoid re-building llvm-gcc. Garrison On Dec 10, 2010, at 12:12, Bob Wilson wrote: > > On Dec 10, 2010, at 6:11 AM, Garrison Venn wrote: > >> Hey Chris, >> >> Ok, so I'm working on creating this trivial patch, for starters, but I'm trying to identify >> a controlled unit test for tblgen. So all of the

...ir /C/projects/src/llvm-2/llvm/test set objdir /C/projects/build/MinGW/llvm-2-1/test set llvmgcc "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread llvm-gcc" set llvmgxx "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread llvm-gcc" ## All variables above are generated by configure. Do Not Edit ## ------------------ llvm-gcc is st...

...X86TargetAsmPrinter()’ previously defined here > make[3]: *** [/llvm/stage1/lib/MC/MCDisassembler/Release/EDDisassembler.o] Error 1 > > > ==== config > > Darwin10 x86_64 (and llvm-gcc from Xcode 3.2.3). > > ../configure --prefix=/opt/llvm-selfhost --without-llvmgcc --without-llvmgxx --disable-bindings --disable-assertions --enable-optimized --enable-targets=x86,x86_64 CC=llvm-gcc CXX=llvm-g++ > > === > > Is somebody else having trouble with this change ? > > > -- Jean-Daniel > > > > > > _______________________________________________ >...

...w Date: Fri, 7 Jan 2005 13:17:09 -0600 (CST) On Fri, 7 Jan 2005, Henrik Bach wrote: >"PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread >llvm-gcc" >set llvmgxx >"PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread >llvm-gcc" >## All variables above are generated by configure. Do Not Edit ## >------------------...

On Fri, 7 Jan 2005, Henrik Bach wrote: > "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread > llvm-gcc" > set llvmgxx > "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread > llvm-gcc" > ## All variables above are generated by configure. Do Not Edit ## > --------------...

...> I committed an extended version of that patch to llvm core and the test suite. > Can you have a look, if it works for you. if I configure like this then the configure script thinks llvm-gcc is not dragonegg: configure --with-llvmgcc="gcc-4.5 -fplugin=path/dragonegg.so" --with-llvmgxx="g++-4.5 -fplugin=path/dragonegg.so" There are several reasons for this. First off, the test if test -x "$LLVMGCC" ; then fails because "g++-4.5 -fplugin=path/dragonegg.so" is indeed not an executable. This test is redundant, since you are about to execute the pro...

.../llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread:/c/projects/src/CMHTREE/PLT/DOS.PLT:/c/WINNT/system32:/c/WINNT:/c/WINNT/System32/Wbem:/c/Program Files/cvsnt:/c/Program Files/7-Zip llvm-gcc" set llvmgxx "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread:/c/projects/src/CMHTREE/PLT/DOS.PLT:/c/WINNT/system32:/c/WINNT:/c/WINNT/System32/Wbem:/c/Program Files/cvsnt:/c/Pro...

...7:09 -0600 (CST) > > On Fri, 7 Jan 2005, Henrik Bach wrote: > >> "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread >> llvm-gcc" >> set llvmgxx >> "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread >> llvm-gcc" >> ## All variables above are generated by configure. Do Not Edit ## >&gt...

On 11/08/2010 03:18 PM, Duncan Sands wrote: > Hi Tobias, > >> I am very interested in using dragonegg as a fortran frontend for the >> LLVM test >> suite, as a start to improve fortran support. >> >> I believe this should be easy, but when I looked into this I had the >> impression >> the nightly tester in the llvm test-suite does not even support

...Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread:/c/projects/src/CMHTREE/PLT/DOS.PLT:/c/WINNT/system32:/c/WINNT:/c/WINNT/System32/Wbem:/c/Program > Files/cvsnt:/c/Program Files/7-Zip llvm-gcc" > set llvmgxx > "PATH=/C/projects/build/MinGW/llvm-2-1/Debug/bin:.:/usr/local/bin:/mingw/bin:/bin:/mingw/bin:/usr/bin:/c/LLVM/tools:/c/perl/5.8.5/bin:/c/perl/5.8.5/bin/MSWin32-x86-multi-thread:/c/projects/src/CMHTREE/PLT/DOS.PLT:/c/WINNT/system32:/c/WINNT:/c/WINNT/System32/Wbem:/c/Program > Files/cv...