From: Gerald Pfeifer <gerald@pfeifer.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Iain Sandoe <idsandoe@googlemail.com>,
Joseph Myers <joseph@codesourcery.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Nathan Sidwell <nathan@acm.org>
Subject: Re: [PATCH] Introduce -nolibstdc++ option
Date: Sat, 11 Feb 2023 10:09:57 +0100 (CET) [thread overview]
Message-ID: <adcea303-5376-d5da-85f1-4b5cea1013a6@pfeifer.com> (raw)
In-Reply-To: <orilor4o2v.fsf@lxoliva.fsfla.org>
On Thu, 23 Jun 2022, Alexandre Oliva via Gcc-patches wrote:
> Introduce -nostdlib++ option
>
> Using g++ to link without libstdc++, as in g++.dg/abi/pure-virtual1.C,
> is error prone, because there's no way to tell g++ to drop libstdc++
> without also dropping libc and any other libraries that the target
> implicitly links in.
% grep -r nostdlib $WWWDOCS
%
Should this be documented in gcc-13/changes.html? Would you mind proposing
a snippet (or going ahead and pushing it)?
Gerald
next prev parent reply other threads:[~2023-02-11 9:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 5:55 Alexandre Oliva
2022-06-21 7:37 ` Richard Biener
2022-06-21 7:53 ` Fangrui Song
2022-06-21 8:03 ` Richard Biener
2022-06-21 8:19 ` Fangrui Song
2022-06-22 0:36 ` Alexandre Oliva
2022-06-22 18:39 ` Iain Sandoe
2022-06-22 23:28 ` Alexandre Oliva
2022-06-22 23:42 ` Fangrui Song
2022-06-23 11:27 ` Alexandre Oliva
2022-06-24 5:23 ` Alexandre Oliva
2022-09-16 11:52 ` Jason Merrill
2022-09-16 11:53 ` Jason Merrill
2022-11-28 17:56 ` Jason Merrill
2023-02-11 9:09 ` Gerald Pfeifer [this message]
2023-03-30 11:23 ` Alexandre Oliva
2023-03-30 13:38 ` Arsen Arsenović
2023-03-30 23:13 ` Gerald Pfeifer
2023-04-06 1:25 ` Alexandre Oliva
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=adcea303-5376-d5da-85f1-4b5cea1013a6@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=idsandoe@googlemail.com \
--cc=joseph@codesourcery.com \
--cc=nathan@acm.org \
--cc=oliva@adacore.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).