Pre-compiled versions of ELLCC are now available via FTP.

Pre-compiled versions of ELLCC are now available via FTP.

[Richard Pennington]

[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]

Hi,

I have made pre-compiled versions of the ELLCC cross compilation tool 
chain available for various Linux targets.
They can be found at ftp://ellcc.org/pub

Targets supported:
ARM (little and big endian)
i386
Mips (little and big endian)
PowerPC
X86_64

 From the README:
The files in this directory contain pre-compiled versions of the ELLCC
cross compiler tool chain. Each tarball is meant to run on a specific
target linux system as indicated by the name, e.g. ellcc-arm-... are
executables that are supposed to run on an little endian ARM Linux box.

All of the executables in these tarballs are statically linked, so they
should run on any reasonably recent Linux box.

Tarball contents:
     C/C++ compiler (ecc, ecc++)
     Assemblers for all targets
     GNU binutils compiled to support all targets.
     GDB compiled to support all the targets.

All of the tarballs contain header files and runtime libraries for all
the targets so you should be able to build for any one of the targets [1].

These tarballs have not been tested, except for the i386 and x86_64 
versions,
because I don't have access to Linux boxes running on the other targets. I
would welcome feedback on how they work for you.

If you have any problems, please post on the ELLCC forum:
     http://ellcc.org/blog/?forum=forum

Please visit http://ellcc.org for more information.

Have fun!

-Rich

[1]: The ARM versions of the executables currently can only target ARM
processors because the ecc compiler became too large to be statically
linked when all processors were supported.

[-- Attachment #2: Type: text/html, Size: 2495 bytes --]

Re: Pre-compiled versions of ELLCC are now available via FTP.

[Szabolcs Nagy]

* Richard Pennington <rich@pennware.com> [2014-02-15 17:02:15 -0600]:
> I have made pre-compiled versions of the ELLCC cross compilation
> tool chain available for various Linux targets.
> They can be found at ftp://ellcc.org/pub

nice

> Tarball contents:
>     C/C++ compiler (ecc, ecc++)
>     Assemblers for all targets
>     GNU binutils compiled to support all targets.
>     GDB compiled to support all the targets.

static gdb is very useful thanks

> because I don't have access to Linux boxes running on the other targets. I
> would welcome feedback on how they work for you.

mips is broken

i used the i386 tool chain to compile to mips target

$ ellcc-i386/bin/ecc -target mips-ellcc-linux hello.c
/tmp/ellcc-i386/bin/ecc-ld: /tmp/ellcc-i386/bin/../libecc/lib/mips/linux/crtbegin.o: warning: linking abicalls files with non-abicalls files
/tmp/ellcc-i386/bin/ecc-ld: /tmp/ellcc-i386/bin/../libecc/lib/mips/linux/libc.a(syscall.o): warning: linking abicalls files with non-abicalls files

the resulting binary works in qemu-mips but crashes on my router
(the same is true for the binaries in the ellcc-mips tool chain)

seems to be an o32 vs eabi issue based on the readelf -h output:

musl-cross:
  ABI Version:                       0
  Flags:                             0x1007, noreorder, pic, cpic, o32, mips1
ellcc:
  ABI Version:                       1
  Flags:                             0x5, noreorder, cpic, mips1

i think the mips asm in musl is written for o32 abi
i'm not sure why it works in qemu