* ELLCC has self hosted.
@ 2013-10-18 23:02 Richard Pennington
2013-10-20 16:49 ` agent
0 siblings, 1 reply; 4+ messages in thread
From: Richard Pennington @ 2013-10-18 23:02 UTC (permalink / raw)
To: musl
[-- 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 --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ELLCC has self hosted.
2013-10-18 23:02 ELLCC has self hosted Richard Pennington
@ 2013-10-20 16:49 ` agent
2013-10-20 21:05 ` Rob Landley
0 siblings, 1 reply; 4+ messages in thread
From: agent @ 2013-10-20 16:49 UTC (permalink / raw)
To: musl
[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]
I understand my question is rather stupid, but what is the most
preferable way to use ecc as a compiler to build itself? Even if I set
cc and cxx variables in the root configure script, it still builds
everything with gcc. Is setting CC and CXX environment variables sufficient?
Dmitry
19.10.2013 05:02, Richard Pennington ?????:
> 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: 7214 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ELLCC has self hosted.
2013-10-20 16:49 ` agent
@ 2013-10-20 21:05 ` Rob Landley
2013-10-21 5:27 ` agent
0 siblings, 1 reply; 4+ messages in thread
From: Rob Landley @ 2013-10-20 21:05 UTC (permalink / raw)
To: musl; +Cc: musl
I'd cc: the relevant parties but this mailing list is misconfigured
with the broken reply-to: tag so I'd have to dig through the backscroll
to find out who they are. Oh well.
On 10/20/2013 11:49:59 AM, agent wrote:
> 19.10.2013 05:02, Richard Pennington ?????:
>> 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.
...
>>
>> That is very cool.
>>
>> -Rich
>>
>
> I understand my question is rather stupid, but what is the most
> preferable way to
> use ecc as a compiler to build itself? Even if I set cc and cxx
> variables in the
> root configure script, it still builds everything with gcc. Is
> setting CC and CXX
> environment variables sufficient?
>
> Dmitry
My question is even dumber: why does the ellcc.org download page say
the last release was a year ago?
Rob
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ELLCC has self hosted.
2013-10-20 21:05 ` Rob Landley
@ 2013-10-21 5:27 ` agent
0 siblings, 0 replies; 4+ messages in thread
From: agent @ 2013-10-21 5:27 UTC (permalink / raw)
To: musl
21.10.2013 03:05, Rob Landley пишет:
> I'd cc: the relevant parties but this mailing list is misconfigured
> with the broken reply-to: tag so I'd have to dig through the
> backscroll to find out who they are. Oh well.
>
> On 10/20/2013 11:49:59 AM, agent wrote:
>> 19.10.2013 05:02, Richard Pennington ?????:
>>> 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.
> ...
>>>
>>> That is very cool.
>>>
>>> -Rich
>>>
>>
>> I understand my question is rather stupid, but what is the most
>> preferable way to
>> use ecc as a compiler to build itself? Even if I set cc and cxx
>> variables in the
>> root configure script, it still builds everything with gcc. Is
>> setting CC and CXX
>> environment variables sufficient?
>>
>> Dmitry
>
> My question is even dumber: why does the ellcc.org download page say
> the last release was a year ago?
>
> Rob
>
There are only binaries on a download page and I don't believe binary
downloads pages any more, so I checked out from SVN repository. I
confirm it is able to compile C and C++ code and link it statically with
musl libc and clang libc++, but I have this trouble with using it to
recompile itself. It compiles about 2 hours on my box so it is quite
hard to experiment with environment variables just to find out it was
still built with GCC.
Dmitry
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-10-21 5:27 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-10-18 23:02 ELLCC has self hosted Richard Pennington
2013-10-20 16:49 ` agent
2013-10-20 21:05 ` Rob Landley
2013-10-21 5:27 ` agent
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).