From: Alexandre Oliva <oliva@adacore.com>
To: Fangrui Song <maskray@google.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Nathan Sidwell <nathan@acm.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH] Introduce -nolibstdc++ option
Date: Tue, 21 Jun 2022 21:36:37 -0300 [thread overview]
Message-ID: <orpmj1bkkq.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAFP8O3Jsq88T_EwCtzKADKR-+oJTNszzekjZ78HOABcd_fGxNQ@mail.gmail.com> (Fangrui Song's message of "Tue, 21 Jun 2022 01:53:34 -0600")
On Jun 21, 2022, Fangrui Song <maskray@google.com> wrote:
> Is this similar to clang -nostdlib++ ?
> When libstdc++ is selected, clang -nostdlib++ removes -lstdc++.
Sounds like they're the same indeed, but the clang option you mention
makes little sense to me, so I'd rather to introduce the one that does.
If someone feels offering this option with the same spelling as clang,
it's easy enough to add a synonym. Now, if others feel we'd be better
off following clang's practices, I don't mind adjusting the patch to use
the same spelling. It's not like this option is going to have much use
one way or another, aside from this testcase.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2022-06-22 0:36 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 [this message]
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
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=orpmj1bkkq.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=maskray@google.com \
--cc=nathan@acm.org \
--cc=richard.guenther@gmail.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).