search for: llvmcc_options

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 atta...

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!

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 apple.com>

.../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

In response to: > Date: Wed, 23 Nov 2011 18:24:16 +0100 > From: Duncan Sands <baldrick at free.fr<mailto:baldrick at free.fr>> > Subject: Re: [LLVMdev] Follow-up questions after successful upgrade to > LLVM 3.0rc4 > To: llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu> > Hi Kevin, >> Since I don't have llvm-gcc installed, I tried to do the

Not that I know of but it's definitely something we could use. The basic idea is to use the test-release.sh script that can be found in llvm source tree under utils/release. $ test-release.sh --help usage: test-release.sh -release X.Y -rc NUM [OPTIONS] -release X.Y The release number to test. -rc NUM The pre-release candidate number. -j NUM Number of compile jobs

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

*I am sorry for making you confused when I presented my problem.* *1. My steps for the test suit building:* (1) cd /home/qali/Src; * // This is my source directory for all application programs* (2) tar xzf llvm-2.8.tgz; * // now, the top directory of source tree is /home/qali/llvm-2.8* (3) cd llvm-2.8/projects (4) svn co http://llvm.org/svn/llvm-project/test-suite/trunk

Hi Dave, Thanks for the results. What platform is this on? And do these failures occur with 2.9? -bw On 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

...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 com...

In response to: > Date: Tue, 22 Nov 2011 21:21:34 +0100 > From: Duncan Sands <baldrick at free.fr<mailto:baldrick at free.fr>> > Subject: Re: [LLVMdev] Follow-up questions after successful upgrade to > LLVM 3.0rc4 > To: llvmdev at cs.uiuc.edu<mailto:llvmdev at cs.uiuc.edu> > Message-ID: <4ECC044E.3020202 at free.fr<mailto:4ECC044E.3020202 at

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 >

---------- Forwarded message ---------- From: Qingan Li <ww345ww at gmail.com> Date: 2011/1/19 Subject: Re: [LLVMdev] About test suits Cont1 To: Eric Christopher <echristo at apple.com> *I am sorry for making you confused when I presented my problem.* *1. My steps for the test suit building:* (1) cd /home/qali/Src; * // This is my source directory for all application

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