similar to: [LLVMdev] compiler-rt with MSVC?

Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] compiler-rt with MSVC?"

2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
On Thu, Oct 23, 2014 at 1:13 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote: > Yes it is. > Are you doing a Debug or Release build? > Using ninja? Release build, cmake + MSVC (not using ninja). Perhaps I have it configured stupidly; I have it as an out-of-tree folder, did: E:\llvm\crt_build>cmake -DLLVM_CONFIG_PATH=E:\llvm\2013\Debug\bin -G "Visual Studio 12"
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
http://llvm.org/bugs/show_bug.cgi?id=21241 ? 2014-10-23 10:18 GMT-07:00 Aaron Ballman <aaron at aaronballman.com>: > On Thu, Oct 23, 2014 at 1:15 PM, Aaron Ballman <aaron at aaronballman.com> wrote: >> On Thu, Oct 23, 2014 at 1:13 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote: >>> Yes it is. >>> Are you doing a Debug or Release build?
2015 Mar 09
5
[LLVMdev] Build failure with compiler-rt on trunk under linux
I've been building clang on linux for a couple of years now, contributing to the testing on Ubuntu, but this one has me stumped: fatal error: 'asm/socket.h' file not found #include <asm/socket.h> [1556/4006] Building CXX object projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.i386.dir/sanitizer_platform_limits_posix.cc.o FAILED:
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
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
2014 Oct 23
2
[LLVMdev] compiler-rt with MSVC 2013
Hello! I'm wondering whether compiler-rt is expected to be buildable with MSVC 2013. I am currently getting: Error 49 error LNK2005: _free already defined in asan_malloc_win.obj E:\llvm\crt_build\lib\asan\MSVCRT.lib(MSVCR120.dll) Which seems to be the only issue (aside from ~50 warnings, which I'll happily work on cleaning up). I get this when I build the ALL_BUILD project in the
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
2013 Jul 31
0
[LLVMdev] Error building compiler-rt
You can disable -Werror by adding the cmake flag -DLLVM_ENABLE_WERROR=OFF, which should let it just ignore that (that's also the default, so you must have turned it on somewhere) On Jul 31, 2013, at 13:09 , Pranav Garg <pranav.garg2107 at gmail.com> wrote: > Hi, > > I am trying to build llvm along with clang and compiler-rt. When I run make, I am getting the following
2013 Jul 31
2
[LLVMdev] Error building compiler-rt
Hi, I see that ENABLE_WERROR is being set to off (the default value) in the config.log in the llvm build. However on grepping for WERROR in the compiler-rt folder I get the following output: pranav at pranav:~/smack-project/llvm-3.4/src/projects/compiler-rt$ grep -Rin WERROR * lib/asan/tests/CMakeLists.txt:38: -Werror lib/asan/asan_malloc_mac.cc:253:// This function is currently unused, and we
2017 Mar 08
2
Use of host/target compiler when building compiler-rt
> On Mar 8, 2017, at 3:14 PM, Chris Bieneman via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > >> On Mar 8, 2017, at 3:08 PM, Hal Finkel <hfinkel at anl.gov <mailto:hfinkel at anl.gov>> wrote: >> >> >> On 03/08/2017 04:55 PM, Chris Bieneman via llvm-dev wrote: >>> David, >>> >>> This is an area that has had a lot
2013 Jul 31
2
[LLVMdev] Error building compiler-rt
Hi, I am trying to build llvm along with clang and compiler-rt. When I run make, I am getting the following compilation error (I tried compiling llvm-3.2, which is what I need for my project, but also tried llvm-3.3 and the current llvm source from the git repository). ... COMPILE: clang_linux/full-x86_64/x86_64:
2014 Sep 06
2
[LLVMdev] [Compiler-RT] [ARM] Where __aeabi_[il]div0 builtins should be implemented?
On Fri, Sep 5, 2014 at 11:32 AM, Jonathan Roelofs <jonathan at codesourcery.com > wrote: > Sergey, > > Not that it'll save you much hassle, but here's an implementation of > __aeabi_idiv0 and __aeabi_ldiv0 that I've been sitting on for a while. > > I vaguely remember compnerd suggesting that I don't commit them to > compiler_rt, but I don't remember
2013 Aug 01
0
[LLVMdev] Error building compiler-rt
Hi Pranav, On Thu, Aug 1, 2013 at 1:54 AM, Pranav Garg <pranav.garg2107 at gmail.com>wrote: > Hi, > > I see that ENABLE_WERROR is being set to off (the default value) in the > config.log in the llvm build. However on grepping for WERROR in the > compiler-rt folder I get the following output: > > pranav at pranav:~/smack-project/llvm-3.4/src/projects/compiler-rt$ grep
2014 Sep 09
2
[LLVMdev] [Compiler-RT] [ARM] Where __aeabi_[il]div0 builtins should be implemented?
On Mon, Sep 8, 2014 at 1:19 AM, Renato Golin <renato.golin at linaro.org> wrote: > > Why not adjust this instead? > > I was just being conservative. I don't know what else depends on this > library and I don't want to change things outside of my scope. > The current implementations actually return 0. Can you point out where that doesn't hold please? If you
2013 Aug 01
2
[LLVMdev] Error building compiler-rt
Dear Alexey, Yes I am sure that the llvm, clang and compiler-rt are synced to the same version. I downloaded them all from git http://llvm.org/docs/GettingStarted.html#git-mirror I think I need compiler-rt for my project but I'll verify it again to see if I can proceed without it. You are correct that compiler-rt is compiled with the just built clang. The complete command that gives an error
2014 Sep 10
2
[LLVMdev] [Compiler-RT] [ARM] Where __aeabi_[il]div0 builtins should be implemented?
On Tue, Sep 9, 2014 at 1:37 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 9 September 2014 02:18, Saleem Abdulrasool <compnerd at compnerd.org> > wrote: > > The current implementations actually return 0. Can you point out where > that > > doesn't hold please? > > With the current implementation... > > int foo(int a) { > return
2015 Feb 13
2
[LLVMdev] [Compiler-rt] i386 is not supported in compiler-rt build
I am trying to build compiler-rt on a x86_64 machine using clang. Command used: CC=clang CXX=clang++ cmake <path to compiler-rt> -DLLVM_CONFIG_PATH=<Path to llvm toolchain>/bin/llvm-config -DCOMPILER_RT_INSTALL_PATH=<Path to llvm toolchain>/lib/clang/3.7.0 after this command on console it prints, -- Compiler-RT supported architectures: x86_64 Instead if I use gcc in above
2013 Aug 01
0
[LLVMdev] Error building compiler-rt
On Thu, Aug 1, 2013 at 5:32 PM, Pranav Garg <pranav.garg2107 at gmail.com>wrote: > Dear Alexey, > > Yes I am sure that the llvm, clang and compiler-rt are synced to the same > version. I downloaded them all from git > http://llvm.org/docs/GettingStarted.html#git-mirror > I think I need compiler-rt for my project but I'll verify it again to see > if I can proceed
2012 Jun 06
2
[LLVMdev] Compile-rt throw error undeclared identifier 'O_CLOEXEC'
Hi, Chatsiri! > ---------- Forwarded message ---------- > From: Chatsiri Ratana <insiderboy at gmail.com> > Date: Wed, Jun 6, 2012 at 2:15 PM > Subject: [LLVMdev] Compile-rt throw error undeclared identifier 'O_CLOEXEC' > To: llvmdev at cs.uiuc.edu > > > Hello All, > > I build LLVM source code version 3.2 from SVN repository. After I > build
2013 Aug 01
2
[LLVMdev] Error building compiler-rt
yes I think that is correct. I wrote a simple program to print if sizeof(uintptr_t) != sizeof(unsigned char *) and when I compile with gcc -m64 and execute it on a 64-bit host (that is different from the 32-bit laptop on which I originally compiled the program), it says the sizes are not equal. Thanks Pranav On Thu, Aug 1, 2013 at 9:29 AM, Alexey Samsonov <samsonov at google.com> wrote: