similar to: [LLVMdev] 32-bit in-tree Polly build with CMake

On 06/07/2012 02:41 PM, Ondřej Hošek wrote: > Hi, > > I was having troubles building LLVM with Polly in-tree using CMake > with LLVM_BUILD_32_BITS on. Turns out CMake considers LLVMPolly a > module, not a shared library, and LLVM_BUILD_32_BITS only makes > provisions for the EXE and SHARED linker flags. Hi, thanks for reporting. == Some bug reporting advice == In this case,

On Thu, Jun 7, 2012 at 3:26 PM, Tobias Grosser <tobias at grosser.es> wrote: > First of all, is this problem platform specific? > We have a 32bit buildbot [1] and it does not report any problems. Do you > understand why. I think so. This is an i?86 build on a x86_64 machine, i.e. with -m32. (gcc specifically, but I am sure that clang would raise the same issue, since this is about

> On Dec 20, 2016, at 5:49 AM, Carsten Mattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > ​Hi again, Teresa. > > Looks like I had forgotten to report back with success > when finally building 3.9.0 in ThinLTO linker mode > back in October. Sorry about that and thanks for > helping me out. I know how important it is to get > success reports as well, as a

Hi Timo: You need to find LLVMConfig.cmake in the binary or install directory tree, not the source tree. Although I don't embed clang/llvm, my config might help you figure it -- clang/llvm installed under (could have used build directory) ~/usr : $ cd /Users/dhinton/projects/cover/build/ && rm -rf * && CC=~/usr/bin/clang CXX=~/usr/bin/clang++ LLVM_DIR=~/usr/lib/cmake/llvm

Sorry my example wasn't helpful. I did take a quick look at rust -- though I didn't download or try to build it -- and they seem to allow you to use an installed or prebuilt version in addition to building it in-tree. However, even when they build it in-tree, they build the whole thing -- see mk/llvm.mk. Good luck... On Mon, Oct 10, 2016 at 1:33 AM, Timo Janssen via llvm-dev <

Hi, an interesting new feature of wine 1.2 is it's 64-bit support. Many Windows chess engines gain about 50-80% speed increase when running at 64-bit. Most provide 32-bit and 64-bit engines. But on my 64-bit Ubuntu 10.04 only an error message appears i.e. with the free Stockfish 1.8. Code: max at ub64:~/Downloads$ uname -a Linux ub64 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:20:59 UTC

Greetings, I've been using LLVM and Clang for a while now, primarily targeting x86 and ARM. Recently, I read the list of open LLVM projects, one of them being "Add JIT support to the SPARC port." Looking further, I saw a May 2010 post from Chris Lattner [2], which basically stated that a future-proof implementation should use LLVM-MC. Is anybody currently working on this project?

> On Oct 24, 2019, at 02:17, Alex Denisov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Chris, > > This is a great initiative and it feels like the right direction. > > I'd like to add another point to the list: using LLVM as a library, i.e. being able to add it as a CMake subproject. > Currently it works pretty good, but some parts can be improved

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

Hi folks, I am confused whether the following is a bug or it is fine Here is the explanation a <- zoo(c(NA,1:9),1:10) Now If I do rollapply(a,FUN=mean,width=3,align="right") I get > rollapply(a,FUN=mean,width=3,align="right") 3 4 5 6 7 8 9 10 NA NA NA NA NA NA NA NA But I shouldn't be getting NA right ? i.e for index 10 I should get (1/3)*(9+8+7)

I wish there was something like the line in config.log that would show the CMake command, but instead I can at least show you the CMakeCache files for my release build and asan build (attached to this email). No lld, so far as I know - believe I'm using gold at the moment for both builds. Did just reproduce this with a clean release build and a clean asanified build from that. Same errors. I

Hi list, I was testing out the "doSMP" package from REvolutionR in my regular R2.11.0 installation and I got the following error message.? Well, one obvious thing is that R2.11.0 was built using "i386-pc-mingw32" which is different from what revoIPC used.? I could just use REvolutionR, but all my R peripherals were set up to work with the regular R2.11.0.? So, I really want

George Karpenkov <ekarpenkov at apple.com> writes: > OK so with Kuba’s help I’ve found the error: with optimization, dead > stripping of produced libraries is enabled, > which removes coverage instrumentation. > > However, this has nothing to do with the move to compiler-rt, so I’m > quite skeptical on whether it has worked > beforehand. > > A trivial fix is to do:

(kcc, george: sorry for the re-send, the first was from a non-list email address) My configuration for building the fuzzers in the LLVM tree doesn't seem to work any more (possibly as of moving libFuzzer to compiler-rt, but there have been a few other changes in the last week or so that may be related). I'm building with a fresh top-of-tree clang and setting -DLLVM_USE_SANITIZER=Address

Over the past few years the LLVM CMake build system has gained a lot of new features, which have powered new workflows and capabilities. This development has largely been individual efforts without focus or long-term direction. The build system is of incredible importance to LLVM as it is a primary interface for contributors to build and test their changes. This year, LLVM is making a huge

> On Aug 24, 2017, at 2:55 PM, Kostya Serebryany <kcc at google.com> wrote: > > Interesting. > This is a relatively new addition (fsanitize-coverage=pc-tables, which is now a part of -fsanitize=fuzzer). > The tests worked (did they? On Mac?) so I thought everything is ok. For tests we never compile the tested target with -O3 (and that wouldn’t be sufficient), and for

Hello, I look for a simple command computing multivariate group means and returning an object of class "matrix" rather than "list". Does any such function exist in standard packages? I'm beginning with R, so I'm sorry if the solution is trivial. Ondra Mikula

I think the simplest fix is something like this: diff --git a/lib/Transforms/Instrumentation/SanitizerCoverage.cpp b/lib/Transforms/Instrumentation/SanitizerCoverage.cpp index c6f0d17f8fe..e81957ab80a 100644 --- a/lib/Transforms/Instrumentation/SanitizerCoverage.cpp +++ b/lib/Transforms/Instrumentation/SanitizerCoverage.cpp @@ -256,6 +256,7 @@ SanitizerCoverageModule::CreateSecStartEnd(Module

Sorry for the delay in writing this up and sending it out, but I wanted to recap the discussion from the roundtable on October 23rd. The roundtable ran for almost two hours and we discussed at most of the main points in my RFC. Thank you everyone who participated and contributed to the discussion! TL;DR: We should move to CMake 3.15 (RFC incoming). We should make `all` really `all`. We should

Which version of CMake? On Tue, Jan 21, 2014 at 10:06 AM, Chandler Carruth <chandlerc at gmail.com>wrote: > Maybe, I'll have to debug. It does seem quite bizarre. > > > On Tue, Jan 21, 2014 at 10:03 AM, Renato Golin <renato.golin at linaro.org>wrote: > >> Chandler, >> >> I may be doing this wrong, but I'm getting a weird error in building