From: "François Dumont" <frs.dumont@gmail.com>
To: Florian Weimer <fweimer@redhat.com>, libstdc++@gcc.gnu.org
Subject: Re: Bare metal C++ with a GNU/Linux toolchain
Date: Wed, 18 May 2022 19:03:57 +0200 [thread overview]
Message-ID: <682cd604-595b-2d02-be08-4e061e956eb0@gmail.com> (raw)
In-Reply-To: <87h75n6qgg.fsf@oldenburg.str.redhat.com>
On 18/05/22 13:16, Florian Weimer via Libstdc++ wrote:
> It seems that it is fairly straightforward to eliminate dependencies on
> libstdc++ if only a C++ subset is used (no exception handling, no RTTI,
> no operator new, etc.).
Those C++ features are in libsup++, not libstdc++.
You should still be able to use full C++ without libstdc++.
I used to do so when working on STLport but it was such a long time ago
that the way we were doing it is surely outdated.
> But once you use abstract classes, you
> necessarily gain a reference to __cxa_pure_virtual.
>
> Would it be possible to document this symbol as interposable, so that
> developers can bring their own definition if they want? If yes, what
> would be the appropriate place for this?
>
> Thanks,
> Florian
>
next prev parent reply other threads:[~2022-05-18 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 11:16 Florian Weimer
2022-05-18 17:03 ` François Dumont [this message]
2022-05-18 19:13 ` Jonathan Wakely
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=682cd604-595b-2d02-be08-4e061e956eb0@gmail.com \
--to=frs.dumont@gmail.com \
--cc=fweimer@redhat.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).