From: Bart Veer <bartv@ecoscentric.com>
To: ecos-maintainers@sources.redhat.com
Subject: [APPROVE] __cxa_pure_virtual()
Date: Thu, 27 Mar 2003 17:56:00 -0000 [thread overview]
Message-ID: <20030327175605.5459FEC6F1@delenn.bartv.net> (raw)
I have just committed a patch to CYGPKG_INFRA to provide an
implementation of __cxa_pure_virtual() that is appropriate for eCos,
overriding the one in libsupc++.
http://sources.redhat.com/ml/ecos-patches/2003-03/msg00209.html
Without this patch any C++ code that uses pure virtual functions will
fail to link. The patch adds a single new function
__cxa_pure_virtual() which will never get called in normal operation,
but which does get referenced by the compiled C++ code. The only time
this function may get called is if the application calls a virtual
function while the object is still being created, which gives
undefined behaviour. Hence the risk is small.
Bart
next reply other threads:[~2003-03-27 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 17:56 Bart Veer [this message]
2003-03-27 18:07 ` Jonathan Larmour
2003-03-27 18:32 ` John Dallaway
2003-03-27 18:57 ` Bart Veer
2003-03-27 19:58 ` Jonathan Larmour
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=20030327175605.5459FEC6F1@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.com \
/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).