search for: llvmcc_option

Nikola Smiljanic <popizdeh at gmail.com> writes: > I'm not sure if this makes a difference but I ran this > > make -j 2 -k LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 ENABLE_PARALLEL_REPORT=1 TEST=simple report > ../../report.txt 2>&1 That does indeed seem to get me further. Thanks! -Dave

...PU E5335 @ 2.00GHz GenuineIntel GNU/Linux I have added a bitcode library to the sample project I have modified the sample project to show my problem -- patch attached. The warning comes from Makefile.rules:1192. The check is performed over LLVMCC, set at Makefile.rules:428-443. Setting depends on LLVMCC_OPTIONS, CLANGPATH, and ENABLE_BUILT_CLANG. Previously -- I have tried with 3699261d3f49d65cee6a645c849c41cdca51a01f -- these vars was set throught the configure script, now they are not set. Thank you for the assistance, speziale.ettore at gmail.com -------------- next part -------------- A non-text att...

greened at obbligato.org (David A. Greene) writes: > Nikola Smiljanic <popizdeh at gmail.com> writes: > >> I'm not sure if this makes a difference but I ran this >> >> make -j 2 -k LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 ENABLE_PARALLEL_REPORT=1 TEST=simple report > ../../report.txt 2>&1 > > That does indeed seem to get me further. Thanks! Failures below. -Dave ******************** TEST (simple) 'sse.expandfft' FAILED! ********...

I'm not sure if this makes a difference but I ran this make -j 2 -k LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 ENABLE_PARALLEL_REPORT=1 TEST=simple report > ../../report.txt 2>&1 inside rc3/Phase3/Release/llvmCore-3.0-rc2.obj/projects/llvm-test On Wed, Nov 9, 2011 at 4:23 PM, David A. Greene <greened at obbligato.org>wrote: > Eric Christopher <echristo at...

.../Linux > I have added a bitcode library to the sample project > > I have modified the sample project to show my problem -- patch attached. > > The warning comes from Makefile.rules:1192. The check is performed over > LLVMCC, set at Makefile.rules:428-443. Setting depends on > LLVMCC_OPTIONS, CLANGPATH, and ENABLE_BUILT_CLANG. Previously -- I have > tried with 3699261d3f49d65cee6a645c849c41cdca51a01f -- these vars was > set throught the configure script, now they are not set. Aha. I see. I'd forgotten to remove that code when I moved the rest of the compiler support out of...

Eric Christopher <echristo at apple.com> writes: > On Nov 8, 2011, at 7:20 PM, David A. Greene wrote: > > I couldn't figure out how to run the test-suite. Are there up-to-date > instructions somewhere? llvm-gcc doesn't exist anymore... > > Easiest is to check out the test-suite branch into projects and then after you configure and build from the top

...suite directory >> and just doing a "./configure". > > the configure should be done in the directory where you built LLVM. Thanks! I tried doing: > cd llvm30/build > ../test-suite-3.0rc4.src/configure . . . configure output > cd ../test-suite-3.0rc4.src > gmake LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 And got the same error as I described previously. On the assumption that my flailing around had contaminated my environment, I decided to start from scratch with the test-suite. So I deleted the test-suite directory, downloaded it again, unpacked it, and retried this s...

...previous releases) The next thing would be to run the test-suite for both releases and use the findRegressions.py (also in utils/release) to compare the output of 3.2 final and the freshly built 3.3 To run the test-suite you run something like this inside llvm/projects/llvm-test directory make -k LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 ENABLE_PARALLEL_REPORT=1 TEST=simple report > ../../../simple-report.txt 2>&1 You report any issues you run into, file bugzilla reports or post to mailing list if you're unsure. This is just to give you some feel for what it actually takes, but the process...

On Sep 28, 2011, at 11:31 PM, Speziale Ettore wrote: > Hi, > > I have updated llvm to the 113aa8612010434069fc5b5e09f6b2667e03e173 git > commit. I have a small llvm project that builds a bitcode library, so I > used MODULE_NAME=foo to build foo.bc. Now, I cannot build the library, > because a compatible compiler cannot be found (Makefile.rules:1052). > > I have seen that

Hi, I have updated llvm to the 113aa8612010434069fc5b5e09f6b2667e03e173 git commit. I have a small llvm project that builds a bitcode library, so I used MODULE_NAME=foo to build foo.bc. Now, I cannot build the library, because a compatible compiler cannot be found (Makefile.rules:1052). I have seen that configure.ac has been modified, so: 1) there is an update in progress? 2) I have to use

...t qali llvm-2.8-ori]$ grep "^LLVM" config.log LLVMCC1='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/cc1' LLVMCC1PLUS='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/cc1plus' LLVMCC_OPTION='llvm-gcc' LLVMGCC='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCCOMMAND='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCDIR='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/..' LLVMGCC_LANGS='c,c++,fortran' LLVMGXX...

...n Nov 10, 2011, at 9:51 AM, David A. Greene wrote: > greened at obbligato.org (David A. Greene) writes: > >> Nikola Smiljanic <popizdeh at gmail.com> writes: >> >>> I'm not sure if this makes a difference but I ran this >>> >>> make -j 2 -k LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 ENABLE_PARALLEL_REPORT=1 TEST=simple report > ../../report.txt 2>&1 >> >> That does indeed seem to get me further. Thanks! > > Failures below. > > -Dave > > ******************** TEST (simple) ...

...ed a bitcode library to the sample project >> >> I have modified the sample project to show my problem -- patch attached. >> >> The warning comes from Makefile.rules:1192. The check is performed over >> LLVMCC, set at Makefile.rules:428-443. Setting depends on >> LLVMCC_OPTIONS, CLANGPATH, and ENABLE_BUILT_CLANG. Previously -- I have >> tried with 3699261d3f49d65cee6a645c849c41cdca51a01f -- these vars was >> set throught the configure script, now they are not set. > Aha. I see. > > I'd forgotten to remove that code when I moved the rest of the co...

...etely obvious how >> to run the test-suite using clang rather than llvm-gcc. I've made a couple >> stabs at it without success. If there is new documentation that I've >> missed, please be kind when you point out where I should have looked. :-} > Pass LLVMCC_OPTION=clang ENABLE_BUILT_CLANG=1 to make when running the testsuite. Duncan, Thanks for the quick response! Since I don't have llvm-gcc installed, I tried to do the configure by doing a "cd" to the test-suite directory and just doing a "./configure". It appeared to do somethin...

On Mon, Apr 29, 2013 at 1:12 PM, Bill Wendling <wendling at apple.com> wrote: > Hear ye! Hear ye! This is a call for testers for the 3.3 release!!! > > What's Expected > --------------- > > You might be asking yourself, "Self, I would like to be an LLVM tester for > the 3.3 release, but I don't know what's involved in being one." Well, ask >

...t qali llvm-2.8-ori]$ grep "^LLVM" config.log LLVMCC1='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/cc1' LLVMCC1PLUS='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.2.1/cc1plus' LLVMCC_OPTION='llvm-gcc' LLVMGCC='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCCOMMAND='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/llvm-gcc' LLVMGCCDIR='/home/qali/build/llvm-gcc4.2-2.8-x86_64-linux/bin/..' LLVMGCC_LANGS='c,c++,fortran' LLVMGXX...

We were successful in upgrading our JIT project to LLVM 3.0rc4 last week, after initially struggling with the various usage and IR changes from V2.9. But we have some follow-up questions: 1) In spite of building and running our tests cleanly with DEBUG+ASSERTS and RELEASE builds, we consistently see a crash when we use a DEBUG build without ASSERTs. The crash appears whenever we use the

*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk

Hear ye! Hear ye! This is a call for testers for the 3.3 release!!! What's Expected --------------- You might be asking yourself, "Self, I would like to be an LLVM tester for the 3.3 release, but I don't know what's involved in being one." Well, ask yourself no more! Not only do I have the answers for you, but talking to yourself will cause people to avoid you. Here's