similar to: [LLVMdev] An LLVM target option matrix.

Hi, As part of my work with Elsa/LLVM I've been trying to wean myself from gcc, I'm using my own preprocessor now (to eliminate gcc -E) and have been calling ld and as directly. To do this, I've set up a version of bunutils (based on 2.18.50) and gdb/insight (based on 6.8) to handle all the LLVM targets (except PIC, see below). The nice thing about gdb 6.8 is that one binary can

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

[~/ellcc/test/source] main% cat printf.c #include <stdio.h> int main(int argc, char** argv) { printf("printf with the string \"%s\"\n", "my string"); } [~/ellcc/test/source] main% ~/ellcc/ellcc/x86-elf-ecc printf.c [~/ellcc/test/source] main% ./a.out printf with the string "my string" [~/ellcc/test/source] main% size a.out text data bss

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

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

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:

A while back (2012) there were a few messages related to using YAML config files to set up how clang would build stuff, especially for cross compilers. My ELLCC project is entirely cross compilation focused, so today I decided to play around with the config file idea. Right now it only handles replacing a "-target foo" option with the options defined in the file foo in the

On 27 November 2013 14:55, Richard Pennington <rich at pennware.com> wrote: > Your link says that clang is using gcc to compile rather than compiling > directly. You might want to look at the ELLCC project, which is designed for > just the sort of cross compilation you are trying to do. http://ellcc.org Hi Rich, No, his output only has gcc to assemble and link:

(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

Today the clang/LLVM based ELLCC compiler (http://ellcc.org) was able to compile an (almost) non-trivial C++ program for a bunch of LLVM supported targets with no gnu licensed libraries. http://ellcc.org/blog/?p=231 Next step: try to compile ELLCC with itself. :-) -Rich -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 11/27/2013 07:57 AM, Rob Stewart wrote: > On 26 November 2013 16:44, Renato Golin <renato.golin at linaro.org> wrote: >> On 26 November 2013 15:36, Rob Stewart <robstewart57 at gmail.com> wrote: >>> $ clang -v -target armv7a-linux-eabi -mcpu=cortex-a9 -mfloat-abi=soft >>> -mfpu=neon helloworld.c >> Hi Rod, > I'm honoured. (But Rob is also OK)

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

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

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

On Friday, January 20, 2012 03:59:14 PM reed kotler wrote: > We are starting to look at the mips16 and micro mips ports. [snip] I'm looking forward to seeing the mips16 and micro mips support. As an aside, the Mips code generator as it exists looks pretty solid so far in my testing. As I've been building the NetBSD library (and other stuff) using my ELLCC copy of clang/LLVM only the

Hi, I recently switched over to using cmake to build my clang/LLVM based ELLCC cross development project (http://ellcc.org). I also recently updated to LLVM svn version 258915 from 258477. I use ELLCC to cross compile all the tools for various Linux targets and for Windows. Yesterday, after updating the LLVM sources, I got the following error when cross building for MinGW: [ 3%] Built

Eli Friedman wrote: > I haven't looked at the rest of the email carefully, but why aren't > you just implementing MULHU and MULHS? There's no point to > implementing the *MUL_LOHI variants if the processor doesn't have > them. I have implemented MULHU and MULHS. But if I take out my *MUL_LOHI stuff, the error I get is [~/ellcc/ellcc] main% ./nios2-elf-ecc -S test.c

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

On Monday, March 05, 2012 02:29:56 AM Duncan Sands wrote: > Hi Richard, > > > I had a little time on my hands this afternoon, so I stole the Clang/LLVM > > demo and modified it to allow compiling for several other targets: > > http://ellcc.org/demo > > does it use the correct header files for the target etc? > > Ciao, Duncan. Yes, it does. The header files