From: Jonathan Wakely <jwakely@redhat.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc Patches <gcc-patches@gcc.gnu.org>,
Rainer Orth <ro@gcc.gnu.org>
Subject: Re: [committed] libstdc++: Fix symbol versioning for Solaris 11.3 [PR103407]
Date: Fri, 18 Mar 2022 12:21:11 +0000 [thread overview]
Message-ID: <CACb0b4kCHU4OTb18Y5pcsD4VnntdUo8-VD63FtcT-XT2O3Bsow@mail.gmail.com> (raw)
In-Reply-To: <yddo8235vld.fsf@CeBiTec.Uni-Bielefeld.DE>
On Fri, 18 Mar 2022 at 11:49, Rainer Orth wrote:
>
> Hi Jonathan,
>
> > Tested x86_64-linux and sparc-sun-solaris2.11 (but 11.3 only).
> >
> > Pushed to trunk.
> >
> > Rainer, this should allow you to continue omitting the
> > _ZSt10from_charsPKcS0_R[def]St12chars_format symbols from the baseline,
> > without the current FAIL. Please check on your other Solaris targets.
>
> I've run bootstraps on i386-pc-solaris2.11 (Solaris 11.3 and 11.4) and
> sparc-sun-solaris2.11 (Solaris 11.4) last night: the abi_check failures
> are gone everywhere.
Hooray!
I did some very brief testing and it seemed like a program linked to
the Solaris 11.3 libstdc++.so.6.0.30 (with from_chars@GLIBCXX_3.4.30)
can still run against libstdc++.so.6.0.30 with
from_chars@GLIBCXX_3.4.29 (which should match what you get on Solaris
11.4 if I correctly fiddled with the versioning). So I don't
understand how the Solaris runtime linker handles symbol versions, but
it seems like there's no backwards compatibility problem for the
Solaris 11.4 build of libstdc++.so.6.0.30.
next prev parent reply other threads:[~2022-03-18 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 21:24 Jonathan Wakely
2022-03-18 11:49 ` Rainer Orth
2022-03-18 12:21 ` Jonathan Wakely [this message]
2022-03-18 12:47 ` Rainer Orth
2022-03-18 12:51 ` Jonathan Wakely
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=CACb0b4kCHU4OTb18Y5pcsD4VnntdUo8-VD63FtcT-XT2O3Bsow@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=ro@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).