From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: sotrdg sotrdg <euloanty@live.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: Is that possible to use clang to build libstdc++ without using GCC?
Date: Mon, 12 Apr 2021 22:57:53 +0100 [thread overview]
Message-ID: <CAH6eHdQHjDxZinhhj-cCfREm3pyUEki9NzeXo0JXuRScyoeamA@mail.gmail.com> (raw)
In-Reply-To: <CH2PR02MB65228B49276C8F30F2B1468DB2709@CH2PR02MB6522.namprd02.prod.outlook.com>
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).
prev parent reply other threads:[~2021-04-12 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 20:34 sotrdg sotrdg
2021-04-12 21:57 ` Jonathan Wakely [this message]
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=CAH6eHdQHjDxZinhhj-cCfREm3pyUEki9NzeXo0JXuRScyoeamA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=euloanty@live.com \
--cc=libstdc++@gcc.gnu.org \
/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.
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).