Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
On 27/10/14 12:07, M. Ziebell wrote: Does clang compile glibc already? At the last GNU Cauldron the speaker said that clang fails because of:[1] - nested functions - VLAIS How did you avoid that problem? musl is known to work fine.
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
Am Wed, 29 Oct 2014 13:39:33 +0100 schrieb Luca Barbato lu_z...@gentoo.org: On 27/10/14 12:07, M. Ziebell wrote: Does clang compile glibc already? At the last GNU Cauldron the speaker said that clang fails because of:[1] - nested functions - VLAIS How did you avoid that problem? musl is known to work fine. True. A good point for the (sub)profile idea. signature.asc Description: PGP signature
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
By the way, any help for maintaining the libc++ stack is very welcome; as you can see from the age of the current snapshots, it's been some time I've not been playing with it. Some notes: - why not adding a clang subprofile ? there's one for amd64-fbsd; I had been able to build a complete stage 3 without too much trouble. There's probably nothing bsd specific there, so moving generic code from there to profiles/features should work. - it'd be worth fixing/improving libunwind support, esp. as you write here on the clang 'spec' parts; I don't remember if there were other issues, but it was a bit pointless if we can't get rid of libgcc_s because of clang (maybe there were even symbol collisions?) - libcxxabi is probably the new way to go instead of libcxxrt; last time I checked there was a chicken and egg problem: libcxxabi needed clang + libc++ to build, so bootstrapping the stack was a bit painful. - there are a few todos in libcxx ebuild (mainly libsupc++ support, but the same could apply to libcxxabi) - it'd be interesting to have stand-alone ebuilds for gcc's crt files; or better, find BSD-like alternatives Alexis.
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
Alexis Ballier wrote: - why not adding a clang subprofile ? there's one for amd64-fbsd; I had been able to build a complete stage 3 without too much trouble. There's probably nothing bsd specific there, so moving generic code from there to profiles/features should work. I'd try to test that at some point. //Peter
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
Does clang compile glibc already? At the last GNU Cauldron the speaker said that clang fails because of:[1] - nested functions - VLAIS How did you avoid that problem? Marco [1] http://www.youtube.ca/watch?v=mmiDwKgn6Holist=PLOGTP9W1DX5U53pPxtWdKkyiqe3GAn6Nd Am Mon, 27 Oct 2014 11:20:00 +0100 schrieb Peter Stuge pe...@stuge.se: Alexis Ballier wrote: - why not adding a clang subprofile ? there's one for amd64-fbsd; I had been able to build a complete stage 3 without too much trouble. There's probably nothing bsd specific there, so moving generic code from there to profiles/features should work. I'd try to test that at some point. //Peter signature.asc Description: PGP signature
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
On Mon, 27 Oct 2014 12:07:25 +0100 M. Ziebell ziebell_ma...@posteo.de wrote: Does clang compile glibc already? At the last GNU Cauldron the speaker said that clang fails because of:[1] - nested functions - VLAIS How did you avoid that problem? by using freebsd's libc :) only problem I can recall is openssl which has been fixed recently afaik
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
Am Mon, 27 Oct 2014 12:10:51 +0100 schrieb Alexis Ballier aball...@gentoo.org: On Mon, 27 Oct 2014 12:07:25 +0100 M. Ziebell ziebell_ma...@posteo.de wrote: Does clang compile glibc already? At the last GNU Cauldron the speaker said that clang fails because of:[1] - nested functions - VLAIS How did you avoid that problem? by using freebsd's libc :) only problem I can recall is openssl which has been fixed recently afaik So glibic is a show stopper or we talk about switching the libc too? signature.asc Description: PGP signature
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
On Mon, 27 Oct 2014 12:29:40 +0100 M. Ziebell ziebell_ma...@posteo.de wrote: Am Mon, 27 Oct 2014 12:10:51 +0100 schrieb Alexis Ballier aball...@gentoo.org: On Mon, 27 Oct 2014 12:07:25 +0100 M. Ziebell ziebell_ma...@posteo.de wrote: Does clang compile glibc already? At the last GNU Cauldron the speaker said that clang fails because of:[1] - nested functions - VLAIS How did you avoid that problem? by using freebsd's libc :) only problem I can recall is openssl which has been fixed recently afaik So glibic is a show stopper or we talk about switching the libc too? it is, but you are the one talking about glibc, I was talking about gentoo/freebsd :)
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
Am 27. Oct 2014, 11:14 schrieb Alexis Ballier aball...@gentoo.org:
By the way, any help for maintaining the libc++ stack is very welcome;
as you can see from the age of the current snapshots, it's been some
time I've not been playing with it.
Some notes:
- why not adding a clang subprofile ? there's one for amd64-fbsd; I had
been able to build a complete stage 3 without too much trouble.
There's probably nothing bsd specific there, so moving
generic code from there to profiles/features should work.
Yes, it looks fairly generic. This is definitely worth a try.
- it'd be worth fixing/improving libunwind support, esp. as you write
here on the clang 'spec' parts; I don't remember if there were other
issues, but it was a bit pointless if we can't get rid of libgcc_s
because of clang (maybe there were even symbol collisions?)
- libcxxabi is probably the new way to go instead of libcxxrt; last
time I checked there was a chicken and egg problem: libcxxabi needed
clang + libc++ to build, so bootstrapping the stack was a bit
painful.
The Toolchain behavior on GNU/Linux is fairly tailored to using gcc at
the moment (just grep for gcc_ on
tools/clang/lib/Driver/{Tools|Toolchain}.cpp).
In order to really pull off a clang/libc++ toolchain independent of gcc
assistance would involve quite a bunch of (preferably upstream) work...
- there are a few todos in libcxx ebuild (mainly libsupc++ support, but
the same could apply to libcxxabi)
- it'd be interesting to have stand-alone ebuilds for gcc's crt files;
or better, find BSD-like alternatives
Alexis.
Best,
Matthias
Re: [gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
Am 27. Oct 2014, 12:07 schrieb M. Ziebell ziebell_ma...@posteo.de: Does clang compile glibc already? At the last GNU Cauldron the speaker said that clang fails because of:[1] - nested functions - VLAIS How did you avoid that problem? Even without this issues there remains the fact that glibc is quite closely coupled to gcc's support libraries (e.g. $ grep dlopen.*gcc_ **/*.c, or pthread's usage of support libraries...). And this is something that won't change anytime soon. After all, glibc is part of the GNU eco system and as such it is perfectly valid to depend on respective compiler.
[gentoo-dev] Clang toolchain [Was: status of bugs blocking gcc-4.8.3]
Could you please blog or add some notes to the wiki about it? I've put up a preliminary version for the toolchain part: https://gist.github.com/tamiko/7e3a0be806fac11f2a35 Best, Matthias
