public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Iain Sandoe <iain@sandoe.co.uk>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	 "libstdc++" <libstdc++@gcc.gnu.org>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Export the __gnu_cxx::zoneinfo_dir_override symbol.
Date: Wed, 4 Jan 2023 17:15:42 +0000	[thread overview]
Message-ID: <CACb0b4mUYG_SgG5Nyru3Lri8ceEyAw0E=XvUpDa6b23=ZJ7Tgg@mail.gmail.com> (raw)
In-Reply-To: <Y7Wz3gNndki9xidy@tucnak>

On Wed, 4 Jan 2023 at 17:14, Jakub Jelinek wrote:
>
> On Wed, Jan 04, 2023 at 03:17:42PM +0000, Jonathan Wakely via Gcc-patches wrote:
> > On Sat, 24 Dec 2022 at 12:21, Iain Sandoe <iain@sandoe.co.uk> wrote:
> > >
> > >
> > >
> > > > On 24 Dec 2022, at 12:12, Jonathan Wakely wrote:
> > > >
> > > >
> > > >
> > > > On Sat, 24 Dec 2022, 11:35 Iain Sandoe via Libstdc++, <libstdc++@gcc.gnu.org> wrote:
> > > >  If this is not the right place to export the symbol (or you do not want
> > > >  to export it in the general case), I can always add a platform-specific
> > > >  file for it.  So far, tested on x86_64-darwin21, wider testing will
> > > >  follow over the holidays.
> > > >
> > > >  OK for trunk?
> > > >
> > > > I'd like to check if this causes the undefined weak symbol to be exported on ELF,
> > >
> > > I’d expect so, since it’s in the common file.
> >
> > hppa-hp-hpux* wants this symbol to be defined anyway (see PR 108228),
> > so please push your patch to trunk.
>
> Isn't it wrong though to export it with GLIBCXX_3.4 symbol version?
> I mean, if it wasn't exported in GCC 3.4 libstdc++.so, then it shouldn't
> be in that symver.  Perhaps GLIBCXX_3.4.31 instead?

Oops, yes! I didn't notice that! I'll move it.

Thanks for catching that.


      reply	other threads:[~2023-01-04 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 11:35 Iain Sandoe
2022-12-24 12:12 ` Jonathan Wakely
2022-12-24 12:20   ` Iain Sandoe
2023-01-04 15:17     ` Jonathan Wakely
2023-01-04 17:14       ` Jakub Jelinek
2023-01-04 17:15         ` Jonathan Wakely [this message]

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='CACb0b4mUYG_SgG5Nyru3Lri8ceEyAw0E=XvUpDa6b23=ZJ7Tgg@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=jakub@redhat.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=libstdc++@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).