From: Richard Pennington <rich@pennware.com>
To: musl@lists.openwall.com
Subject: ELLCC has self hosted.
Date: Fri, 18 Oct 2013 18:02:36 -0500 [thread overview]
Message-ID: <5261BE0C.2000904@pennware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
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 interesting side note: The compiler was 12MB smaller after it built
itself.
ct-fw-88 ellcc 622 % size */Release+Asserts/bin/ecc
text data bss dec hex filename
52415858 2152024 84768 54652650 341eeea
llvm-build/Release+Asserts/bin/ecc
40222706 2117136 135416 42475258 2881efa
llvm-build-self/Release+Asserts/bin/ecc
Even more interesting, it was compiled statically. No dynamic libraries
needed:
ct-fw-88 ellcc 623 % ldd */Release+Asserts/bin/ecc
llvm-build/Release+Asserts/bin/ecc:
linux-vdso.so.1 => (0x00007fff2ffff000)
libz.so.1 => /lib64/libz.so.1 (0x00007facd87e1000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007facd85c4000)
libncurses.so.5 => /lib64/libncurses.so.5 (0x00007facd837c000)
librt.so.1 => /lib64/librt.so.1 (0x00007facd8173000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007facd7f6f000)
libstdc++.so.6 => /home/de023789/gnulocal/lib64/libstdc++.so.6
(0x00007facd7c6e000)
libm.so.6 => /lib64/libm.so.6 (0x00007facd7a18000)
libgcc_s.so.1 => /home/de023789/gnulocal/lib64/libgcc_s.so.1
(0x00007facd7803000)
libc.so.6 => /lib64/libc.so.6 (0x00007facd74a5000)
/lib64/ld-linux-x86-64.so.2 (0x00007facd89f7000)
llvm-build-self/Release+Asserts/bin/ecc:
not a dynamic executable
ct-fw-88 ellcc 624 %
That is very cool.
-Rich
[-- Attachment #2: Type: text/html, Size: 6323 bytes --]
next reply other threads:[~2013-10-18 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 23:02 Richard Pennington [this message]
2013-10-20 16:49 ` agent
2013-10-20 21:05 ` Rob Landley
2013-10-21 5:27 ` agent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5261BE0C.2000904@pennware.com \
--to=rich@pennware.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).