public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: Ville Voutilainen <ville.voutilainen@gmail.com>,
	libstdc++ <libstdc++@gcc.gnu.org>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [v3 PATCH] Implement LWG 2221, No formatted output operator for nullptr
Date: Fri, 11 Jan 2019 11:01:00 -0000	[thread overview]
Message-ID: <20190111110059.GF15627@redhat.com> (raw)
In-Reply-To: <yddh8efd0kb.fsf@CeBiTec.Uni-Bielefeld.DE>

On 11/01/19 10:07 +0100, Rainer Orth wrote:
>Hi Jonathan,
>
>>>this patch broke Solaris bootstrap:
>>>
>>>ld: fatal: libstdc++-symbols.ver-sun: 7117: symbol 'std::basic_ostream<char, std::char_traits<char> >::operator<<(decltype(nullptr))': symbol version conflict
>>>ld: fatal: libstdc++-symbols.ver-sun: 7119: symbol 'std::basic_ostream<wchar_t, std::char_traits<wchar_t> >::operator<<(decltype(nullptr))': symbol version conflict
>>>
>>>ld: fatal: libstdc++-symbols.ver-sun: 7117: symbol '_ZNSolsEDn': symbol version conflict
>>>ld: fatal: libstdc++-symbols.ver-sun: 7119: symbol '_ZNSt13basic_ostreamIwSt11char_traitsIwEElsEDn': symbol version conflict
>>>
>>>Again, there were two matches for those two symbols:
>>>
>>>  GLIBCXX_3.4
>>>    ##_ZNSolsE*[^Dg] (glob)
>>>    _ZNSolsEDn;
>>>  GLIBCXX_3.4.26
>>>    ##_ZNSolsEDn (glob)
>>>    _ZNSolsEDn;
>>>
>>>  GLIBCXX_3.4
>>>    ##_ZNSt13basic_ostreamIwSt11char_traitsIwEElsE*[^Dg] (glob)
>>>    _ZNSt13basic_ostreamIwSt11char_traitsIwEElsEDn;
>>>  GLIBCXX_3.4.26
>>>    ##_ZNSt13basic_ostreamIwSt11char_traitsIwEElsEDn (glob)
>>>    _ZNSt13basic_ostreamIwSt11char_traitsIwEElsEDn;
>>>
>>>ISTM that the patterns were backwards.  The following patch fixes this
>>>and allowed i386-pc-solaris2.11 bootstrap to complete without
>>>regressions relative to the last successful one.
>>
>> I think what I should have done is change [^g] to [^gn]. That
>> preserves the original behaviour (don't match the ppc64 long double
>> symbols) but also excludes the new symbols, which end in 'n'.
>>
>> Maybe the attached patch would be better though. It matches every
>> basic_ostream::operator<<(T) for any scalar T except 'g', and adds a
>> second pattern to match basic_ostream::operator<<(T*) for various T.
>> But neither of those matches the new operator<<(nullptr_t) overload.
>
>it allowed me to link libstdc++.so, too.  For my patch I'd only been
>going from the ld errors and the matching patterns in the generated
>libstdc++.map-sun, not knowing the background here.

THanks for checking it. I've committed the patch now.

>> FWIW I did run my symbol checker script, but it gets lots of false
>> positives because it doesn't understand the #if preprocessor
>> conditions, so it sees lots of false positive duplicates. I need to
>> make it smarter for it to be useful here.
>
>Indeed: the variation possible here can be a total PITA ;-)

I've managed to cobble together a pipeline with sed and cpp that
allows me to test the linker script properly. It found some conflicts
that still remain but presumably aren't present on Solaris because
HAVE_SYMVER_SYMBOL_RENAMING_RUNTIME_SUPPORT is not defined.

There's one remaining conflict, which https://gcc.gnu.org/PR88125
covers. 

I'll commit a patch for those shortly.

      reply	other threads:[~2019-01-11 11:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 21:08 Ville Voutilainen
2017-12-04 23:04 ` Jonathan Wakely
2019-01-10 13:15   ` Jonathan Wakely
2019-01-10 21:27     ` Rainer Orth
2019-01-11  0:01       ` Jonathan Wakely
2019-01-11  9:07         ` Rainer Orth
2019-01-11 11:01           ` 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=20190111110059.GF15627@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ro@cebitec.uni-bielefeld.de \
    --cc=ville.voutilainen@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).