similar to: [LLVMdev] The first small step to an ELLCC release.

Hi, I've updated the musl version of the clang/LLVM based ELLCC compiler suite to use musl release 0.9.14. As usual the musl guys have been doing a great job. The new release looks great! http://ellcc.org I've also started to port libunwind into ELLCC. That's the last step for a fully non-gnu run-time environment: libcxx/libcxxabi/libunwind/musl/compiler-rt for C and C++ under

As part of my ELLCC project (http://ellcc.org), I build clang/LLVM on my native x86_64 Linux box and then use it to compile itself. For further sanity checking, I then use that copy to cross compile for other targets (arm, armeb, i386, microblaze, mips, mipsel, ppc, and x86_64). After updating to a recent TOT revision, r195452, I get a strange error when cross compiling for the i386:

Hi cschen, Here are the test scripts which I written when I was developing ARM exception handling support: https://github.com/loganchien/libcxx-scripts The script should work on Debian wheezy (cross-compiling from amd64 to armhf.) In general, here are the necessary steps: 1. Get a working arm-linux-gnueabihf gcc/g++ toolchain (for the headers and libraries) 2. Setup the include search path

> ELLCC (http://ellcc.org), my clang/LLVM based cross development tool chain for > ARM, Microblaze, Mips, Power PC, and X86, now incorporates musl > (http://www.etalabs.net/musl) as its standard C library for Linux. musl is a > MIT licensed, highly POSIX compliant library offering high performance and a > small foot print. I spent several weeks evaluating musl before deciding to use

Hi, I've been working on combining LLVM, clang, the NetBSD standard C library, compiler-rt, QEMU, GDB, and GNU binutils as a cross compilation environment. My goal is to target small embedded systems, but I think that what I'm working on may be of interest to other LLVM/clang developers as I have been able to use the environment to fix several code generation issues in LLVM. As of

ELLCC (http://ellcc.org), my clang/LLVM based cross development tool chain for ARM, Microblaze, Mips, Power PC, and X86, now incorporates musl (http://www.etalabs.net/musl) as its standard C library for Linux. musl is a MIT licensed, highly POSIX compliant library offering high performance and a small foot print. I spent several weeks evaluating musl before deciding to use it in ELLCC. The

(Fixed the cfe email address) On 12/18/2015 09:34 PM, Tim Northover wrote: > On 18 December 2015 at 19:15, Richard Pennington via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> It turns out that it can with some simple patches. > This sounds really cool. I think we should seriously consider putting > these patches into LLVM mainline. > >> Information on

The clang/LLVM based ELLCC project (http://ellcc.org), after having reached a huge milestone ( http://ellcc.org/blog/?p=231) has now successfully compiled itself. The steps were: 1. Use gcc to build the compiler with Linux standard libraries. 2. Use ecc to build itself with libc++, libc++ABI, libunwind, musl, and compiler-rt 3. Use the newly built compiler to build itself again. One

Well, at least it works on some programs across all arches. That was some great testing you've done for us. :-) Thanks! Renato On 28 Oct 2016 23:51, "Richard Pennington" <rich at pennware.com> wrote: > On 10/28/2016 05:27 PM, Renato Golin wrote: > >> On 28 October 2016 at 23:02, Rui Ueyama via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >>

As some of you may be aware, I've been fooling around with using clang/LLVM as a cross compilation environment. Actually "fooling around" is a little bit of an understatement. I've been working on it in on and off for quite a while. :-) I just wanted to give a brief update on the current status. First, the projects goals: * Use LLVM/clang as a cross compiler for arm, i386,

On 10/28/2016 05:27 PM, Renato Golin wrote: > On 28 October 2016 at 23:02, Rui Ueyama via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Awesome results! > I'm surprised! LLD is barely working on ARM at the moment. :) > [snip] My mistake. ARM worked for small programs, but lld failed for clang with a bunch of these errors: /home/rich/ellcc-release/bin/ld.lld: error:

Geting a seg fault. Have not investigted the cause. rkotler at mipsswbrd002:~/richard$ tar vfxz ~/Downloads/ellcc-mips-linux-2014-Mar-24-07-32-26.tgz rkotler at mipsswbrd002:~/richard/ellcc/bin$ gdb ./ecc GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are

ELLCC is a compilation tool chain based on clang/LLVM, libc++ and the musl standard C library for Linux. Recently I was asked if ELLCC pre-built binaries could be used to build clang/LLVM TOT. It turns out that it can with some simple patches. This is a simple way to bootstrap clang/LLVM on an arbitrary Linux system that either doesn't have GCC or has a version of GCC that is too old to

Hi, I asked this question a few days ago and didn't get any responses. I thought I'd try again with a little more detail. I am trying to cross compile my clang/LLVM based ELLCC cross development tools project (http://ellcc.org) on a Mac. I am targeting ARM/Linux. The build fails while building FileCheck (or tbl-gen or any of the other build tools built during the

> after realizing that it wasn't actually a backend that targetted c++ > (which might be useful) Exact same thing just happened to me.. it's not obvious, especially when reading the llc info: $ llc -version Registered Targets: arm - ARM arm64 - ARM64 (little endian) cpp - C++ backend x86 - 32-bit X86: Pentium-Pro and above x86-64

There was, a long time ago, a backend that actually targetted C. It was deleted in 2012 at r153307. On Sun, May 22, 2016 at 8:37 AM, Stefan Gränitz <stefan.graenitz at gmail.com> wrote: > after realizing that it wasn't actually a backend that targetted c++ > (which might be useful) > > Exact same thing just happened to me.. it's not obvious, especially when > reading

On Fri, Oct 28, 2016 at 2:56 PM, Richard Pennington via cfe-dev < cfe-dev at lists.llvm.org> wrote: > With all the talk about using lld on the list, I thought it would be > interesting to try using it in my clang based ELLCC cross compilation tool > chain. http://ellcc.org > > The change was simple, since I use configuration files to tell clang how > to compile, where to

With all the talk about using lld on the list, I thought it would be interesting to try using it in my clang based ELLCC cross compilation tool chain. http://ellcc.org The change was simple, since I use configuration files to tell clang how to compile, where to find libraries, etc. I described the config files here: http://ellcc.org/blog/?p=13246 All I had to do was change the linker

I compiled a program and standard library using clang/LLVM and found the results interesting: text data bss dec hex filename 141312 4076 16668 162056 27908 bzip2.arm 131764 4076 16668 152508 253bc bzip2.armv7 134748 4048 16624 155420 25f1c bzip2.i386 259112 4028 16732 279872 44540 bzip2.microblaze 168044 4040 16816 188900 2e1e4

Hi, Did this make it into review / commit? It's probably too late for 3.6 if it didn't, but I'd love to see it in 3.7. It would also be nice if this support could be something a bit more general in LLVM, rather than specifically in clang, so that other llvm tools (e.g. llvm-objdump) could take advantage of a similar format for target description files if they need something more