public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/59894] Force use of the default new/delete
Date: Mon, 24 Feb 2014 14:01:00 -0000 [thread overview]
Message-ID: <bug-59894-4-qRSpZFowjH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59894-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59894
--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #0)
> PR 59893 considers a different path using LTO to inline at link time the
> definition from libsupc++.
Note that doing both at the same time:
1) provide an inline version of new
2) LTO-link with libsupc++
might interact badly (or not, I haven't checked). We should test it and if
needed warn about it in the documentation or preferably find a workaround.
prev parent reply other threads:[~2014-02-24 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 21:36 [Bug libstdc++/59894] New: " glisse at gcc dot gnu.org
2014-01-20 21:57 ` [Bug libstdc++/59894] " trippels at gcc dot gnu.org
2014-01-20 22:07 ` glisse at gcc dot gnu.org
2014-01-21 9:40 ` redi at gcc dot gnu.org
2014-02-24 14:01 ` glisse at gcc dot gnu.org [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=bug-59894-4-qRSpZFowjH@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).