public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: libstdc++@gcc.gnu.org
Subject: Bare metal C++ with a GNU/Linux toolchain
Date: Wed, 18 May 2022 13:16:31 +0200	[thread overview]
Message-ID: <87h75n6qgg.fsf@oldenburg.str.redhat.com> (raw)

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.).  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


             reply	other threads:[~2022-05-18 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 11:16 Florian Weimer [this message]
2022-05-18 17:03 ` François Dumont
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=87h75n6qgg.fsf@oldenburg.str.redhat.com \
    --to=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).