Displaying 20 results from an estimated 900 matches similar to: "llvm cross compilation issue"
2016 Feb 10
4
Guidance on cross compiling LLVM with mingw-w64 and cmake
I need to build libLLVM (individual static libraries are fine at the
moment) using mingw-w64 cross compilers, i686-w64-mingw32-gcc and
(separately) x86_64-w64-mingw32-gcc. I'd like this to work from both
Linux and Cygwin build environments. With autotools, this worked fine:
../configure --host=i686-w64-mingw32 and that's it (with mingw32-gcc-c++
installed on Fedora 23, also works fine on
2013 May 29
0
[LLVMdev] compiler-rt tests in cmake?
> Android runtime is special, we build it in a separate build tree
configured with
> -DCMAKE_TOOLCHAIN_FILE=$LLVM_CHECKOUT/cmake/platforms/Android.cmake
This worked great, thanks! Would you mind tweaking Android.cmake so that I
can override the location of the C compiler? The current version forces me
to use the just-built-clang and that the new build directory be in a
sibling directory.
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
On Thu, Oct 23, 2014 at 2:24 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote:
> I don't think this is the right approach.
>
> Currently we intentionally define malloc etc without changing the
> names and (when stuff works ok) the linker just links all the mem
> allocator calls with calls to our RTL. This is kind of a link-time
> interception.
How could that work
2013 May 28
4
[LLVMdev] compiler-rt tests in cmake?
Okay, dropping gcc 4.4.3 makes sense. How do you feel about using clang
3.2 (and the upcoming 3.3) instead of tip-of-the-trunk clang? It looks
like everything works great, but that you just need to make those UB tests
'unsupported' since they fail with "libclang_rt.ubsan was built without
__int128 support".
Thanks,
Greg
On Mon, May 27, 2013 at 12:36 AM, Alexey Samsonov
2017 Oct 18
2
LLVM cross-compilation cmake issues
I'm an idiot and sent to llvm-commits instead of llvm-dev. Fixing.
On 10/17/17, 5:09 PM, "llvm-commits on behalf of Shoaib Meenai via llvm-commits" <llvm-commits-bounces at lists.llvm.org on behalf of llvm-commits at lists.llvm.org> wrote:
Hi all (CC beanz for cmake advice),
I'm running into a cmake problem when I try to cross-compile a
2017 Aug 24
3
Building LLVM's fuzzers
George Karpenkov <ekarpenkov at apple.com> writes:
> Should -DCMAKE_CXX_COMPILER be also specified?
CMake is smart enough to infer that from C_COMPILER:
% grep CMAKE_CXX_COMPILER CMakeCache.txt
CMAKE_CXX_COMPILER:FILEPATH=/Users/bogner/llvm-lkgc/bin/clang++
>> On Aug 24, 2017, at 11:29 AM, Justin Bogner <mail at justinbogner.com> wrote:
>>
>> (kcc, george:
2014 Oct 23
3
[LLVMdev] compiler-rt with MSVC 2013
On Thu, Oct 23, 2014 at 2:46 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote:
> 2014-10-23 11:34 GMT-07:00 Aaron Ballman <aaron at aaronballman.com>:
>> On Thu, Oct 23, 2014 at 2:24 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote:
>>> I don't think this is the right approach.
>>>
>>> Currently we intentionally define malloc etc
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
I think this issue is that we were not using the INTERCEPTOR macros to
define these functions. The following patch seems to work for me to
get the build linking again, however, I cannot test -- when I run
check-asan, I get:
2> lit.py: lit.common.cfg:59: fatal: Invalid llvm_tools_dir config
attribute: 'E:/llvm/2013/$(Configuration)/bin'
~Aaron
On Thu, Oct 23, 2014 at 1:20 PM, Aaron
2017 Dec 26
2
Bootstrapping LLVM+LLD with GCC toolchain failure
Hello,
I have a working GCC toolchain and wanted to use LLVM tooling instead.
Following the instructions on the website I set up my build directory
and have lld as an internal project under tools/. I'd like to make use
of lld in stage 2 of the build and thought -DLLVM_ENABLE_LLD was the
correct option to pass. However, adding this options makes the
configure step fail, complaining that the
2017 Aug 24
3
Building LLVM's fuzzers
> 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
2016 May 03
4
Linux/ARM: Segfault issue when we build clang sources including __thread variable using -O2 flag
A few days ago, I tried to change the optimization flag from -O0 to -O2 to
speed up the execution of the application on Ubuntu/ARM 14.04 32 bit.
When I compiled the source code with -O2 flag instead of -O0 flag, I could
not run the application normally by getting always the segmentation fault.
Here is debugging information with GDB command in case of that. As you can
see, we could not execute
2016 Nov 25
27
[Bug 98852] New: Nvidia graphics card fan not running or to slow, danger of overheating
https://bugs.freedesktop.org/show_bug.cgi?id=98852
Bug ID: 98852
Summary: Nvidia graphics card fan not running or to slow,
danger of overheating
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
2017 Aug 24
5
Building LLVM's fuzzers
(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
2020 Apr 10
2
Opus CMake build support for Apple frameworks
Hi Simon,
CMake 3.14 add support for crosscompiling iOS, tvOS and watchOS
https://cmake.org/cmake/help/v3.14/manual/cmake-toolchains.7.html#cross-compiling-for-ios-tvos-or-watchos
Can you clarify what your patch does?
//Marcus
cmake-toolchains(7) — CMake 3.14.7 Documentation<https://cmake.org/cmake/help/v3.14/manual/cmake-toolchains.7.html#cross-compiling-for-ios-tvos-or-watchos>
The
2016 Sep 27
4
(Thin)LTO llvm build
On Tue, Sep 27, 2016 at 6:53 AM, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
>
> > On Sep 27, 2016, at 2:18 AM, Carsten Mattner <carstenmattner at gmail.com>
> wrote:
> >
> >> On Mon, Sep 26, 2016 at 11:02 PM, Teresa Johnson <tejohnson at google.com>
> wrote:
> >> I'll either need to get a reproducer from you and/or try to repro
2017 Aug 24
2
Building LLVM's fuzzers
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
2017 Aug 24
4
Building LLVM's fuzzers
On Thu, Aug 24, 2017 at 3:21 PM, Kostya Serebryany via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
>
> On Thu, Aug 24, 2017 at 3:20 PM, Justin Bogner <mail at justinbogner.com>
> wrote:
>
>> I think the simplest fix is something like this:
>>
>> diff --git a/lib/Transforms/Instrumentation/SanitizerCoverage.cpp
>>
2017 Aug 24
3
Building LLVM's fuzzers
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:
2010 Aug 02
0
[LLVMdev] CMake broken?
Tom Care <tcare at apple.com> writes:
> This was after starting with an empty build directory. It seems to
> work if I omit -DLLVM_TARGETS_TO_BUILD=X86, but a few days ago this
> was working with just this target.
Yep. I can replicate the problem on Linux with
mkdir foo && cd foo
cmake -DLLVM_TARGETS_TO_BUILD=X86 ../llvm
I'll investigate a bit.
2017 Aug 24
3
Building LLVM's fuzzers
On Thu, Aug 24, 2017 at 3:38 PM, Kostya Serebryany <kcc at google.com> wrote:
>
>
> On Thu, Aug 24, 2017 at 3:35 PM, Peter Collingbourne <peter at pcc.me.uk>
> wrote:
>
>> On Thu, Aug 24, 2017 at 3:21 PM, Kostya Serebryany via llvm-dev <
>> llvm-dev at lists.llvm.org> wrote:
>>
>>>
>>>
>>> On Thu, Aug 24, 2017 at 3:20