* Is that possible to use clang to build libstdc++ without using GCC?
@ 2021-04-12 20:34 sotrdg sotrdg
2021-04-12 21:57 ` Jonathan Wakely
0 siblings, 1 reply; 2+ messages in thread
From: sotrdg sotrdg @ 2021-04-12 20:34 UTC (permalink / raw)
To: libstdc++
I want to build a cross compiler for webassembly. GCC backend has not yet supported wasm. However, technically it should be possible to use clang to build libstdc++.
The reason I do not want to use libc++ is that it is slow, bloat and no full C++20 ranges. (They just finish the concepts part, not the ranges part)
Then we will have a clang + libstdc++ targetting wasm compiler.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Is that possible to use clang to build libstdc++ without using GCC?
2021-04-12 20:34 Is that possible to use clang to build libstdc++ without using GCC? sotrdg sotrdg
@ 2021-04-12 21:57 ` Jonathan Wakely
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Wakely @ 2021-04-12 21:57 UTC (permalink / raw)
To: sotrdg sotrdg; +Cc: libstdc++
On Mon, 12 Apr 2021 at 22:40, sotrdg sotrdg via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> I want to build a cross compiler for webassembly. GCC backend has not yet supported wasm. However, technically it should be possible to use clang to build libstdc++.
It should be possible, but might need some changes. We make no attempt
at portability in the libstdc++-v3/src/*/*.cc files, so they just make
use of GCC extensions without checking if they are supported (because
we know they are supported by GCC, and those files are only compiled
by GCC).
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-04-12 21:58 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-12 20:34 Is that possible to use clang to build libstdc++ without using GCC? sotrdg sotrdg
2021-04-12 21:57 ` Jonathan Wakely
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 read-only IMAP folder(s) and NNTP newsgroup(s).