similar to: [LLVMdev] A Microblaze bug.

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

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

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

LLVM Weekly - #39, Sep 29th 2014 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/39>. Welcome to the thirty-ninth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex Bradbury](http://asbradbury.org).

On Thursday, December 08, 2011 02:46:39 AM Csaba Raduly wrote: > On Wed, Dec 7, 2011 at 9:43 PM, Richard Pennington wrote: > > 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

On Thu, Dec 8, 2011 at 11:46 PM, Richard Pennington wrote: > On Thursday, December 08, 2011 02:46:39 AM Csaba Raduly wrote: >> On Wed, Dec 7, 2011 at 9:43 PM, Richard Pennington  wrote: >> > I compiled a program and standard library using clang/LLVM and found the >> > results interesting: >> > >> >   text    data     bss     dec     hex filename

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

On Wed, Dec 7, 2011 at 9:43 PM, Richard Pennington wrote: > 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 >

> 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

Sorry if this is a duplicate: I tried to send it last night and it didn't go through. I'm trimming some text to see if it helps. I have a simple program that fails on the Microblaze: int main() { unsigned long long x, y; x = 100; y = 0x8000000000000000ULL; return !(x > y); } As you can see, the test case compares two unsigned long long values. To try to track

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

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

[~/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

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

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:

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

On Jan 29, 2010, at 9:42 AM, Wesley Peck wrote: > I have been working on a LLVM backend for the MicroBlaze soft-processor: > http://www.xilinx.com/tools/microblaze.htm > http://en.wikipedia.org/wiki/MicroBlaze Very Cool! > Attached is the initial MicroBlaze patch. It does the following: > 1. Adds mblaze as a target in configure and configure.ac > 2. Adds mblaze specific

I have been working on a LLVM backend for the MicroBlaze (http://en.wikipedia.org/wiki/MicroBlaze ) soft-processor. At this point the backend is partially functional but by no means complete. I was curious as to wether the LLVM developers would prefer to merge the backend into the main tree now and then accept patches on the backend until it was fully functional or if they prefer to wait