public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/105417] [11/12/13 Regression] powerpc64le-linux abilist changes based on --with-long-double-format=
Date: Fri, 29 Apr 2022 10:46:13 +0000	[thread overview]
Message-ID: <bug-105417-4-CFp5nUHTX2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105417-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105417

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #3)
> Are those cxx11 symbols never needed and so it was a mistake that they've
> been exported?

I thought they were needed, but I've now convinced myself they aren't. The
public headers do not declare explicit instantiations for those symbols, so
user code doesn't know that they're (sometimes) defined in libstdc++.so and so
user code will contain implicit instantiations of them. So the definitions
exported from the library are never needed outside the library itself.

  parent reply	other threads:[~2022-04-29 10:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  8:27 [Bug libstdc++/105417] New: [11/12 " jakub at gcc dot gnu.org
2022-04-28  8:27 ` [Bug libstdc++/105417] " jakub at gcc dot gnu.org
2022-04-28  8:29 ` redi at gcc dot gnu.org
2022-04-28  8:33 ` jakub at gcc dot gnu.org
2022-04-28 13:21 ` jakub at gcc dot gnu.org
2022-04-29 10:46 ` redi at gcc dot gnu.org [this message]
2022-04-29 10:49 ` [Bug libstdc++/105417] [11/12/13 " redi at gcc dot gnu.org
2022-04-29 10:56 ` jakub at gcc dot gnu.org
2022-04-29 13:00 ` redi at gcc dot gnu.org
2022-04-29 13:41 ` cvs-commit at gcc dot gnu.org
2022-04-29 13:44 ` cvs-commit at gcc dot gnu.org
2022-04-29 14:18 ` [Bug libstdc++/105417] [11 " redi at gcc dot gnu.org
2023-05-29 10:06 ` jakub at gcc dot gnu.org

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-105417-4-CFp5nUHTX2@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).