similar to: [LLVMdev] enabling openmp cmake build in llvm tree

Hi Zachary: I was able to reproduce the greendragon results locally (OSX), and fix the problem by excluding 'debuginfo-tests' from check-clang -- this prevents them from being added twice, once for check-clang and again for check-debuginfo. Below are the minimized patches I used to reproduce and fix the problem -- based on your originals. I've verified these patches work when

> On Dec 6, 2017, at 10:10 AM, Zachary Turner <zturner at google.com> wrote: > > Adrian, Mike, Chris? Any update on this? I've temporarily switched to working on something different, but I plan to be back on this in a couple of weeks. It's been a month since my first revert of this CL, which seems like a reasonable amount of lead-time to deal with issues surrounding

> On Dec 6, 2017, at 10:21 AM, Zachary Turner <zturner at google.com> wrote: > > Can I have some assurance that if it fails again, someone will look into who has access to the builders so I don't have to keep doing speculative commits? Sure. I did this last time and I promise to also do it this time. -- adrian > > On Wed, Dec 6, 2017 at 10:13 AM Adrian Prantl

Hi there. I was trying to rebuild LLVM, this time with Clang, and after getting the last svn version, I got this error during cmake: CMake Error: Error in cmake code at <dir>/llvm/projects/CMakeLists.txt:7: Parse error. Function missing ending ")". Instead found left paren with text "(". The line is "if(NOT (${entry} STREQUAL

This will be used by Clang to show full build information when LLVM_APPEND_VC_REV is enabled and LLVM/Clang are built from Git. Also try to figure-out repository URL and revision from Git mirror parsing git-svn-id: footer from last commit (if present). --- cmake/modules/VersionFromVCS.cmake | 55 ++++++++++++++++++++++++++++---------- 1 file changed, 41 insertions(+), 14 deletions(-) diff --git

Currently, cmake policies are manually maintained by each project. This is done via a set of `cmake_policy()` commands following the initial `cmake_minimum_required()` command at the top of each CMakeLists.txt project file. Somewhat surprisingly, these sets are local to each project and independent of each other -- even for in-tree builds containing multiple sub-projects. This is because cmake

On 30 April 2015 at 10:06, Hal Finkel <hfinkel at anl.gov> wrote: >> >> I'd like to resurrect the discussion on replacing libgomp with >> libiomp as the default OpenMP runtime library linked with -fopenmp. >> >> >> For reference, the previous discussion is accessible there: >>

On Fri, May 1, 2015 at 1:57 PM, Chandler Carruth <chandlerc at google.com> wrote: > On Fri, May 1, 2015 at 10:46 AM Jack Howarth < > howarth.mailing.lists at gmail.com> wrote: > >> On Thu, Apr 30, 2015 at 5:51 PM, Chandler Carruth <chandlerc at google.com> >> wrote: >> >>> On Thu, Apr 30, 2015 at 6:52 AM Andrey Bokhanko < >>>

On Thu, Apr 30, 2015 at 5:51 PM, Chandler Carruth <chandlerc at google.com> wrote: > On Thu, Apr 30, 2015 at 6:52 AM Andrey Bokhanko <andreybokhanko at gmail.com> > wrote: > >> All, >> >> I'd like to resurrect the discussion on replacing libgomp with libiomp as >> the default OpenMP runtime library linked with -fopenmp. >> > > Just for

Chandler, Thanks for the reply -- I always included you in libiomp supporters camp; it is good to see I wasn't mistaken! ;-) On Fri, May 1, 2015 at 12:51 AM, Chandler Carruth <chandlerc at google.com> wrote: > Is there no way to support libgomp here as well? I don't say this to hold > up changing the defaults in any way, just curious. =] > No, sorry. libgomp doesn't

On Thu, Apr 30, 2015 at 9:06 PM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- >> From: "Andrey Bokhanko" <andreybokhanko at gmail.com> >> To: "cfe-dev" <cfe-dev at cs.uiuc.edu>, "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>, "Douglas Gregor" >> <dgregor at apple.com>,

I means visual studio c++ 2008, do you build clang+llvm with .sln files, and these files are generated by cmake? I do of that. And because vs c++ can't recognize path such a:/filepath/.. Properlyn it's recognized as a:/filepath So we need change /.. to /../ or /../. 2009/8/6, Daniel Dunbar <daniel at zuster.org>: > I don't understand this problem, I have built clang on

Chandler: 1) I completely agree with the comments some others have made about us needing to make it clear that this isn't some Intel-only thing, it’s the LLVM OpenMP runtime. Some suggestions that I think would make sense to help here: … code owner discussion elided since Chris has endorsed Andrey… - Clearly updating the readme and such would be appropriate. Certainly, no problem with

On Thu, Apr 30, 2015 at 2:51 PM, Chandler Carruth <chandlerc at google.com> wrote: > On Thu, Apr 30, 2015 at 6:52 AM Andrey Bokhanko <andreybokhanko at gmail.com> > wrote: > >> All, >> >> I'd like to resurrect the discussion on replacing libgomp with libiomp as >> the default OpenMP runtime library linked with -fopenmp. >> > > Just for

Jack, Could you, please, submit a bug report? -- including steps to reproduce (where you got imageMagick sources, how exactly you compiled them, etc) Andrey On Fri, May 1, 2015 at 3:56 PM, Jack Howarth <howarth.mailing.lists at gmail.com> wrote: > > > On Fri, May 1, 2015 at 4:45 AM, Andrey Bokhanko <andreybokhanko at gmail.com> > wrote: >> >> Chandler,

Hal, On Thu, Apr 30, 2015 at 5:06 PM, Hal Finkel <hfinkel at anl.gov> wrote: > We need to get the build system integration committed and the buildbots > updated to compile it > If you are speaking on libiomp buidbots, they are already established: http://lab.llvm.org:8011/builders/libiomp5-clang-x86_64-linux-debian

I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig into it once I get a chance -- traveling so, my access is a bit sketchy right now. I'll see if I can grab the logs and let you know if I find anything interesting. On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote: > That change was added specifically to workaround a failure

All, I'd like to resurrect the discussion on replacing libgomp with libiomp as the default OpenMP runtime library linked with -fopenmp. For reference, the previous discussion is accessible there: http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20140217/thread.html#99461 We are very close to getting *full* OpenMP 3.1 specification supported in clang (only one (!) clause is not

I have winebottle 1.2.3 installed which includes Wine but wonder it Wine 1.4 the latest stable version will update Wine. Also do I download the binary version or the other I am confused about all the options. Can anyone help please?

On 02/06/2014 08:12 AM, Alexey Samsonov wrote: > Please note that it makes a lot of sense to built compiler-rt (and sanitizers) with just-built > Clang. In fact, even though we should support building it with another compilers (gcc, MSVC), > using just-built-Clang should be a default scenario, like it is in configure+make build. This is possible with CMake using the ExternalProject