Displaying 20 results from an estimated 600 matches similar to: "[LLVMdev] Building Compiler-RT on Windows"
2015 Feb 20
2
[LLVMdev] Building Compiler-RT on Windows
Has anyone built Compiler-RT on Windows? I am attempting to compile it for
ARM, but I get errors from CMake. It appears to be trying to pass VC++
flags to Clang. I am using a version of Clang built from trunk.
PS D:\llvm\arm_test\compiler-rt-build> cmake -G Ninja
-DCMAKE_C_COMPILER=clang.exe -DCMAKE_CXX_COMPILER=clang++.exe -DCM
AKE_RC_COMPILER=rc.exe -DCMAKE_CXX_FLAGS=""
2015 Feb 26
0
[LLVMdev] Building Compiler-RT on Windows
On Fri, Feb 20, 2015 at 12:54 PM, Timur Iskhodzhanov <timurrrr at google.com>
wrote:
> [+Saleem]
>
>
> On Fri Feb 20 2015 at 10:31:04 PM Daniel Dilts <diltsman at gmail.com> wrote:
>
>> I am using CMake 3.1.2.
>>
>> On Fri, Feb 20, 2015 at 10:00 AM, Alexey Samsonov <vonosmas at gmail.com>
>> wrote:
>>
>>> It looks like your
2015 Feb 26
1
[LLVMdev] Building Compiler-RT on Windows
I am attempting to build for bare-metal ARM.
On Wed, Feb 25, 2015 at 9:13 PM, Saleem Abdulrasool <compnerd at compnerd.org>
wrote:
>
>
> On Fri, Feb 20, 2015 at 12:54 PM, Timur Iskhodzhanov <timurrrr at google.com>
> wrote:
>
>> [+Saleem]
>>
>>
>> On Fri Feb 20 2015 at 10:31:04 PM Daniel Dilts <diltsman at gmail.com>
>> wrote:
2014 Oct 02
2
[LLVMdev] Header File Not Found?
I'm having a strange problem compiling with VS 2013. It's not finding a
header file that's there in one of the header file search dirs.
Here's the compile command (with the names changed to protect the
innocent ;-)
1> C:\Program Files (x86)\LLVM\msbuild-bin\CL.exe /c
/IC:\[top-level-dir]\[source-dir]\
/IC:\[top-level-dir]\[source-dir]\[sub-dir-1]
2016 Feb 13
2
r260758 broke windows build
On 2/12/2016 9:47 PM, Vince Harron wrote:
> Are you building LLDB? Im guessing that is where the failure is
I'm building LLVM. The failure in the buildbot happens when compiling
HexagonFrameLowering.cpp:
----------
FAILED: C:\PROGRA~2\MICROS~1.0\VC\bin\cl.exe /nologo /TP /DWIN32
/D_WINDOWS /W4 -wd4141 -wd4146 -wd4180 -wd4244 -wd4258 -wd4267 -wd4291
-wd4345 -wd4351 -wd4355 -wd4456
2013 Jul 24
6
[LLVMdev] Transitioning build to cmake
I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system.
There are a couple of issues that I still haven't been able to work out yet and would like to know if these are just configuration issues on my side or bugs I should file at bugs.llvm.org:
1) libclang_rt
It looks like the cmake build is missing some runtime
2020 Aug 09
3
Switching to Ninja
Sigh. I ask for your indulgence yet again.
I installed Ninja and deleted my old build tree. When I run CMake now, I'm told that it can't find the compilers and assembler. So, of course, I need to put a compiler toolset on my path. I tried MinGW but was instantly reminded that it doesn't have localtime_s. So I tried to find the Visual Studio binaries and located four different
2015 Mar 14
2
[LLVMdev] Add a backend
Is there documentation somewhere about exactly what the function is
supposed to do, or do I have to figure it out from existing examples?
On Sat, Mar 14, 2015 at 12:13 AM, Anton Korobeynikov <
anton at korobeynikov.info> wrote:
> You have to provide this function and initialize the whole MC
> infrastructure.
>
> See e.g. lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp
>
>
2015 Mar 14
2
[LLVMdev] Add a backend
Yes, llvm::InitializeAllTargetMCs(void) does seem to be autogenerated. It
is _LLVMInitializeFooTargetMC that I can't find documented anywhere.
On Sat, Mar 14, 2015 at 12:05 AM, Anton Korobeynikov <
anton at korobeynikov.info> wrote:
> This function is autogenerated. You need also to change top-level
> configure / cmake files.
>
> On Sat, Mar 14, 2015 at 8:38 AM, Daniel
2013 Jul 24
0
[LLVMdev] Transitioning build to cmake
On Jul 24, 2013, at 11:11 AM, Jeremy Huddleston Sequoia wrote:
> I recently took a stab at changing the MacPorts llvm-3.4 port from the configure-based build system to the cmake-based build system.
>
> There are a couple of issues that I still haven't been able to work out yet and would like to know if these are just configuration issues on my side or bugs I should file at
2015 May 06
4
[LLVMdev] LLD improvement plan
On Wed, May 6, 2015 at 6:22 AM, Chris Lattner <clattner at apple.com> wrote:
> On May 5, 2015, at 6:47 PM, Daniel Dilts <diltsman at gmail.com> wrote:
>
> Take a look at how debuggers have migrated through the years. They too
>>
>> used to have their own script format. Now most (all?) popular debuggers
>> do scripting through embedding an actual programming
2015 May 06
3
[LLVMdev] LLD improvement plan
On Wed, May 6, 2015 at 5:30 PM, Daniel Dilts <diltsman at gmail.com> wrote:
>
>
> On Wed, May 6, 2015 at 12:51 AM, Will Newton <will.newton at gmail.com> wrote:
>>
>> On Wed, May 6, 2015 at 6:22 AM, Chris Lattner <clattner at apple.com> wrote:
>> > On May 5, 2015, at 6:47 PM, Daniel Dilts <diltsman at gmail.com> wrote:
>> >
>>
2015 Mar 09
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
Hi,
I have been using LLVM+Clang in my project for some time and it has been
working just fine up to now (I am currently using version 3.5.1).
However, with version 3.6 having just been released, I thought I would give
it a try and update my code to use MCJIT rather than the now discontinued
JIT. Well, this proved to be a relatively smooth process, and everything is
now working fine on
2019 Sep 05
3
Building LLVM with LLVM
Hi folks!
I'm trying to build LLVM with LLVM on Ubuntu using the commands below.
Building it with the GNU stuff (cpp, gcc, g++ and binutils packages) works,
but after removing it, moving LLVM to /usr/local and symlinking /usr/bin/ld
to ld.lld, I'm getting the following:
=== snip ===
-- The C compiler identification is Clang 8.0.1
-- The CXX compiler identification is Clang 8.0.1
-- The
2014 Oct 31
3
[LLVMdev] Tree conflict on checkout
I am getting the following error while trying to checkout LLVM. I deleted
my local copy (no changes) just in case something was causing the issue,
but it didn't fix it.
Tree conflict on 'llvm\test\Bindings\Ocaml'
> local dir unversioned, incoming dir add upon update
Select: (r) mark resolved, (p) postpone, (q) quit resolution, (h) help:
-------------- next part --------------
2020 Feb 04
2
CMakeTestCCompiler fails
Trunk clang does not pass CMake C Compiler test like below:
CMake Error at
/home/usr4/c74014i/opt/cmake-3.16.3-Linux-x86_64/share/cmake-3.16/Modules/CMakeTestCCompiler.cmake:60
(message):
The C compiler
"/home/usr4/c74014i/opt/clang/current/bin/clang"
is not able to compile a simple test program.
It fails with the following output:
Change Dir:
2016 Apr 04
2
XOR CommandLine arguments
Both arguments require a string. Sorry, I forgot to mention that.
On Mon, Apr 4, 2016 at 12:02 PM, Sean Silva <chisophugis at gmail.com> wrote:
> Could you do something like `-mode={if,od}` and make the option required?
>
> -- Sean Silva
>
> On Mon, Apr 4, 2016 at 11:54 AM, Daniel Dilts via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> With the
2019 Jun 08
2
Help Building LLVM for Android
Hey Guys,
I'm working on a project in Android related to System-level Audio DSP
Effects for Tuning Android Audio. I want to leverage Faust (
https://faust.grame.fr/) to allow users to program their own filters.
Faust provides a libfaust implementation which includes a JIT Compiler
which leverages LLVM and seems to be the best path for me to use.
Unfortunately I'm having problems
2015 Mar 29
2
[LLVMdev] How to Cross Compile libcompiler_rt Static Library?
I need to correct myself. It is possible to cross compile it on Windows,
but not using the provided build systems.
On Sun, Mar 29, 2015 at 12:52 PM, Daniel Dilts <diltsman at gmail.com> wrote:
> I asked about this same question in the past (month or three ago). It is
> not possible to cross compile compiler-rt on Windows. If you want to cross
> compile you should use the make
2015 Mar 09
2
[LLVMdev] LLVM 3.6: problems building on Windows using MSVC 2013
Sorry, I am using CMake+JOM or CMake+Ninja, if Ninja is available on the developer’s machine. Either way, it fails in both cases with a message similar to the one I included below (which was obtained using CMake+Ninja).
Just in case, my (current) CMakeLists.txt file can be found at here