public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "qiu.chaofan at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100912] powerpc64le: ieee128 long double incorrectly printed when using shared libstdc++
Date: Wed, 13 Oct 2021 08:56:47 +0000	[thread overview]
Message-ID: <bug-100912-4-l8YWOuCWg2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100912-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Qiu Chaofan <qiu.chaofan at outlook dot com> ---
By changing the order of linked objects (move .libs/compatibility-ldbl.o
.libs/compatibility-ldbl-alt128.o .libs/compatibility-ldbl-alt128-cxx11.o after
the series of convenience archives), the result under `-mabi=ieeelongdouble` is
correct, but `-mabi=ibmlongdouble` goes wrong.

Removing `--gc-sections` and use nm, we’ll see both
`__vsnprintfieee128@@GLIBC_2.32` and `vsnprintf@@GLIBC_2.17` exist. So it looks
all the symbols (with the same name,
_ZSt16__convert_from_vRKP15__locale_structPciPKcz) were visited by the linker,
but only the first one was kept.

  parent reply	other threads:[~2021-10-13  8:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 18:51 [Bug libstdc++/100912] New: " msc at linux dot ibm.com
2021-06-04 22:27 ` [Bug target/100912] " pinskia at gcc dot gnu.org
2021-06-05 10:51 ` redi at gcc dot gnu.org
2021-06-07 13:27 ` msc at linux dot ibm.com
2021-06-07 13:50 ` msc at linux dot ibm.com
2021-10-11 10:08 ` [Bug libstdc++/100912] " qiu.chaofan at outlook dot com
2021-10-13  8:56 ` qiu.chaofan at outlook dot com [this message]
2021-10-13  9:16 ` redi at gcc dot gnu.org
2021-10-21  3:47 ` qiu.chaofan at outlook dot com
2021-12-06  6:26 ` qiu.chaofan at outlook dot com
2022-01-10  9:57 ` qiu.chaofan at outlook dot com
2022-01-10 10:01 ` redi at gcc dot gnu.org
2022-02-14 17:27 ` cvs-commit at gcc dot gnu.org
2022-02-14 17:29 ` redi 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-100912-4-l8YWOuCWg2@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).