similar to: [LLVMdev] llvm-lit: failing test due to messages in stderr

On 01/15/2018 10:52 AM, Michael Kruse via llvm-dev wrote: > Dear community, > > for our goal to make polyhedral optimization available in the main > LLVM source, we will need the Integer Set Library (isl)[1]. It is the > main dependency of Polly, but would be required even if we do not > directly import Polly. > > I already prepared a patch [2], unfortunately without

2015-08-29 14:45 GMT+08:00 Martell Malone <martellmalone at gmail.com>: > Why are there two ways to compile LLVM? >> make and cmake! >> What's the difference of those two ways? > > > make and cmake are used together not separately. > cmake is a high level generator that creates a makefile for make > > I compile llvm according to this website(

In the root llvm/CMakeLists.txt we have: if( ${PYTHON_VERSION_STRING} VERSION_LESS 2.7 ) message(FATAL_ERROR "Python 2.7 or newer is required") endif() But lit seems to still be stuck in a Python 2.5 world. For example, detectCPUs is redundant now that we have multiprocessing.cpu_count() (multiprocessing requires >=2.6). And there are a bunch of other Python 2.5 workarounds

Hi Andreas, > In practice that'll mean adding the correct directives to > CMakeLists.txt, not Makefile, right? That's what the targets I looked > at did. LLVM can be built using either CMake or the GNU Autotools. Your backend ought to provide support for both build systems, so you should create a CMakeLists.txt as well as a Makefile in your sub-directory. The Makefile appears

Great! I'll circle around to this at some point. Despite the "obvious" nature of it I still am wary of underestimating the cruftiness of the buildbots, so I'll probably do it some time at night when the bots are mostly green so that I can easily see if any bots *are* broken by this. -- Sean Silva On Tue, Feb 23, 2016 at 6:55 PM, Chris Matthews <chris.matthews at

This sounds like a good idea to me! I can’t think of any common platform where you can’t get 2.7. Lets get rid of that legacy cruft! > On Feb 23, 2016, at 1:32 PM, Eric Christopher <echristo at gmail.com> wrote: > > Seems reasonable to me. Chris? > > On Mon, Feb 22, 2016, 8:40 PM Sean Silva via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at

Dear all, Recently I've considering using LIT for my benchmark testing framework, and the only reference for LLVM-LIT is the man page and some READMEs. I don't find any documentations on config, which seems to be quite important to the tool. If I use lit outside LLVM source tree and use on my own test files, LIT marks them as 'unresolved'. So are there any documentations I can

Description =========== This patch adds support of CMake meta build system, so you can generate Unix makefiles, VS 6.0-2017 projects and many more. Features ======== * Win32 and Linux tested * Travis CI test added * Generates working Visual Studio 6.0-2017 solutions * Generates working Unix Makefile * Supported options (<option> - <default value>): * `ENABLE_FLOATING_POINT` - on

> > We may just not use those functions anymore - do you have a list of these? > Yes, i've started to make up a list of those functions, but it haven't finished yet. > This is more concerning - maybe it's a windows specific problem that came > along? > Not sure, i haven't look yet for CMake checking code itself. By the way, i'm using FreeBSD. Or to say it

On Tue, Feb 7, 2012 at 4:58 AM, Carsten Sinz <carsten.sinz at kit.edu> wrote: > Perhaps some of you might be interested in this: > -- Carsten > > > ################################################################## > > *---------------------------------------------------* > * LLBMC: The Low-Level Bounded Model Checker * > * for C (and C++)

greetings I am new to this list. I have recently compiled llvm-3.3 from sources. My machine has these: --cpu -amd64 --os- clbfs 64bit -linux3 series kernel --C/C++ compiler -modern versions gcc My preferred build tool is cmake. llvm is needed for MesaLib and the autotools build of llvm allows this option:- --enable-experimental-targets=R600 ( for example described here:

On 2015-05-26 11:31 PM, Cristian Adam wrote: > Yes please. CMake support is somehow mandatory for any C/C++ project > nowadays. Fascinating. Do the Visual Studio projects it generates know how to invoke cmake to update themselves? > Death to autotools! But that's just my ignorance speaking :-) I don't like autotools _or_ cmake. Fortunately, I'm not libogg's only user...

arrowdodger <6yearold at gmail.com> writes: >> Or to say it with other words: patches welcome. > > So, how should i proceed? Make CMake-generated config to be identical to > autotools one? That would be a good thing. Please note that some checks are a bit tricky. A function that on platform A is on header foo.h on another platform may be on bar.h. Furthermore, cmake's

Hi Marcus, Thanks for the fixes. I did some more cmake build testing and encountered a few issues: The option -DFORTIFY_SOURCE=2 should be -D_FORTIFY_SOURCE=2, as the macro has a leading underscore. In the autotools build it defines this if it is not already defined (m4/ax_add_fortify_source.m4). When custom modes are not enabled, the cmake build is nevertheless installing the include file

Hi Micheal, thanks for moving this forward! 2018-01-15 17:52 GMT+01:00 Michael Kruse via llvm-dev < llvm-dev at lists.llvm.org>: > Dear community, > > for our goal to make polyhedral optimization available in the main > LLVM source, we will need the Integer Set Library (isl)[1]. It is the > main dependency of Polly, but would be required even if we do not > directly

> Can you answer my question on how to set the version-string correct > when generating tarballs out of the release_38 Git branch? > ( I generated source-tarballs out of my local Git repositories, see below. ) [ llvm.src/CMakeLists.txt ] ... if(NOT DEFINED LLVM_VERSION_MAJOR) set(LLVM_VERSION_MAJOR 3) endif() if(NOT DEFINED LLVM_VERSION_MINOR) set(LLVM_VERSION_MINOR 8) endif() if(NOT

Johannes, This patch seems to be causing test failures when I just do "ninja check", without running "ninja" or "ninja all" first. $ CC=clang CXX=clang++ cmake -G Ninja ~/git/llvm-project/llvm -DLLVM_USE_LINKER=lld -DLLVM_PARALLEL_LINK_JOBS=4 -DCMAKE_BUILD_TYPE=Release -DLLVM_TARGETS_TO_BUILD=X86 && ninja check [...] FAIL: LLVM ::

Daniel, I'm just a 42 year old former NeXT and Apple Dev who back in Mechanical Engineering is excited about OpenCL/OpenGL and all that is with LLVM/Clang, but I've got to say that even though my plans include learning Python for various areas of development the last I want to deal with is a Build system needing it to compile a Compiler Suite. Autotools is a bag of hurt, always has

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