similar to: [LLVMdev] Building compiler-rt for foreign target?

[+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? >>

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:

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

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=""

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

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

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 > >

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 --------------

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: >> > >>

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

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

In attempting to add a backend I came across the documentation here: http://llvm.org/docs/WritingAnLLVMBackend.html The section on the build system seems to be out of date, or maybe I don't understand it. I copied the Sparc target to a directory (Foo for the example), added Foo to the subdirectories list in llvm\lib\Target\LLVMBuild.txt and to LLVM_ALL_TARGETS in llvm\CMakeLists.txt. I

> > > 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

> 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

Hi, Is there a way to (cross-)build the compiler-rt for an ARM-EABI target? I read the comments in the associated Makefile, so I understand it cannot be easily done when builing clang. However, is there a way to build the compiler-rt for another plaftorm but the host, once clang & llvm have been successfully built? Thanks, Manu.

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

I was attempting to cross compile on Windows. I ended up having to find the list in the CMake build system (not very hard) and manually creating a makefile to compile them. Took maybe 2 hours total. On Sun, Mar 29, 2015 at 1:28 PM, Chao Yan <yanchao2012 at gmail.com> wrote: > > 2015-03-29 15:11 GMT-05:00 Daniel Dilts <diltsman at gmail.com>: > >> I need to correct

I'm trying to build compiler-rt for bare-metal arm-none-eabi targets. I don't need any of the existing compiler-rt functionality(though the builtin(s) may be nice). I want to extend it with custom functionality for the arm-none-eabi targets. Can anyone give me some pointers on how to go about doing this. I'm currently doing a combined build of llvm, clang and compiler-rt for both

> Looks as though whomever implemented the call to __aeabi_idiv0 wanted > to be conservative for non EABI targets. How could it prevent him from providing default implementation of __aeabi_idiv0() for EABI targets? > AFAIK, gnueabi targets recognize all EABI functions, so that should > work well. Not sure I understand you, nothing in compiler-rt defines these functions, they are

Hi, There are several places in compiler-rt which refer to __aeabi_idiv0. For example, in lib/builtins/arm/udivsi3.S: #ifdef __ARM_EABI__ b __aeabi_idiv0 #else JMP(lr) #endif At the same time there is no definition of it. It looks as if it was done intentionally so that third-party could provide custom handler for division by zero. IMHO It's not very consistent and looks odd as