similar to: [LLVMdev] Add a backend

Displaying 20 results from an estimated 1100 matches similar to: "[LLVMdev] Add a backend"

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
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 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
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 --------------
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 Feb 20
3
[LLVMdev] Building Compiler-RT on Windows
[+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 command fails early in CMake TryCompile tests. Does >> (your version of) CMake supports using Clang on Windows at all? >>
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
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:
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 May 06
2
[LLVMdev] LLD improvement plan
> > > Linker scripts are worse than everything - except for the alternatives > that > > we know about. Any particular suggestions here? > > I very much care about the functionality provided by linker scripts (for > embedded systems and kernel work), but I do agree that most current > script formats are hard to use, debug, reason about, etc... I have > often
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
2014 Aug 22
10
[LLVMdev] [RFC] Raising LLVM minimum required MSVC version to 2013 for trunk
> On Aug 22, 2014, at 9:53 AM, Daniel Dilts <diltsman at gmail.com> wrote: > > On Fri, Aug 22, 2014 at 9:42 AM, Chris Bieneman <beanz at apple.com <mailto:beanz at apple.com>> wrote: > Starting a new thread to loop in cfe-dev and lldb-dev. For those not following along there has been a thread on llvm-dev about moving the minimum required Visual Studio version to
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=""
2010 Dec 25
4
[LLVMdev] Question of autotools about adding a new target for LLVM
Hello all, I am a beginner of LLVM and want to add a new Target for LLVM. I follow the document (http://llvm.org/docs/WritingAnLLVMBackend.html) to modify autotools/configure.ac. However when I type ./AutoRegen.sh There is an error that "Your autoconf was not detected as being 2.60" I download the source of autoconf 2.60 and install it. And there is the other error that "Your
2015 Apr 28
2
[LLVMdev] Building compiler-rt for foreign target?
I'm developing something for an ARMv7-A system in big-endian mode. I'm trying to use clang as the compiler for it. Things have been going well so far, but I've hit a point where the generated code is depending on functions which are implemented in compiler-rt. Since I'm doing the building on an amd64 machine, the compiler-rt that I have only targets x86/amd64. So, I have three
2012 Jul 06
4
[LLVMdev] New backend
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello devs, I'd like to ask for some advise about adding a backend. I followed the steps at http://llvm.org/docs/WritingAnLLVMBackend.html (also adding the backend to the configure script, so it compiles (on Linux) with LLVM 3.1. However, llvm-build fails with: llvm[0]: Constructing LLVMBuild project information. Usage: llvm-build [options]
2015 Mar 29
2
[LLVMdev] How to Cross Compile libcompiler_rt Static Library?
2015-03-29 3:33 GMT-05:00 Ed Schouten <ed at 80386.nl>: > I am cross-compiling compiler-rt for my specific use-case. That said, > I'm cross-compiling from x86-64 to x86-64, but for a different ABI. > This is what I use: > > > https://github.com/NuxiNL/cloudlibc/wiki/Building-runtime-libraries#user-content-compiler-rt > > -DCMAKE_CROSSCOMPILING=True > > As
2011 Dec 12
2
[LLVMdev] buildbot failure
On Dec 12, 2011, at 2:51 PM, Tony Linthicum wrote: > On 12/12/2011 4:49 PM, Eric Christopher wrote: >> >> >> On Dec 12, 2011, at 2:41 PM, Eric Christopher wrote: >> >>> >>> On Dec 12, 2011, at 2:36 PM, Tony Linthicum wrote: >>> >>>> On 12/12/2011 4:28 PM, Jakob Stoklund Olesen wrote: >>>>> >>>>>
2017 Jan 03
2
LLVM WebAssembly target
Hello. Excuse me. Why CMakeLists.txt from llvm-3.9.1.src does not contain WebAssembly target? So, it is like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ X86 XCore ) but not like set(LLVM_ALL_TARGETS AArch64 AMDGPU ARM BPF Hexagon Mips MSP430 NVPTX PowerPC Sparc SystemZ Webassembly X86
2011 Dec 13
0
[LLVMdev] buildbot failure
I'm hitting this. Is there ETA for the fix? Evan On Dec 12, 2011, at 2:58 PM, Daniel Dunbar wrote: > > On Dec 12, 2011, at 2:51 PM, Tony Linthicum wrote: > >> On 12/12/2011 4:49 PM, Eric Christopher wrote: >>> >>> >>> On Dec 12, 2011, at 2:41 PM, Eric Christopher wrote: >>> >>>> >>>> On Dec 12, 2011, at 2:36