public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org
Subject: [v3] Update Solaris baselines
Date: Wed, 08 Apr 2015 13:52:00 -0000	[thread overview]
Message-ID: <yddh9sq6833.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)

[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]

With the GCC 5 release approaching, it's time to update the Solaris
baselines again.

This patch does just that and is pretty much straightforward:

* With one exception, all new symbols are in the GLIBCXX_3.4.21 and
  CXXABI_1.3.9 versions.

* On Solaris/x86 only (obviously), we have

+OBJECT:0:CXXABI_FLOAT128
+OBJECT:16:_ZTIg@@CXXABI_FLOAT128
+OBJECT:2:_ZTSg@@CXXABI_FLOAT128
+OBJECT:32:_ZTIPKg@@CXXABI_FLOAT128
+OBJECT:32:_ZTIPg@@CXXABI_FLOAT128
+OBJECT:3:_ZTSPg@@CXXABI_FLOAT128
+OBJECT:4:_ZTSPKg@@CXXABI_FLOAT128

  For the moment (considering how late we are in the release cycle),
  I've decided to use the SPARC version for the common baseline, so
  those symbols show up as added on x86.

* On Solaris 11, there are two additonal symbols beyond those in Solaris
  10:

+FUNC:std::__cxx11::basic_stringbuf<char, std::char_traits<char>, std::allocator<char> >::~basic_stringbuf()@@GLIBCXX_3.4.21
+FUNC:std::__cxx11::basic_stringbuf<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >::~basic_stringbuf()@@GLIBCXX_3.4.21

  They are from src/c++98/complex_io.o and src/c++11/sstream-inst.o,
  respectively.  No idea where this difference comes from, it might be
  related to the fact that Solaris 11 has COMDAT group support while
  Solaris 10 does not.  I've again decided to live with this difference
  and use the Solaris 10 version of the baselines.

Bootstrapped without regressions on i386-pc-solaris2.1[01] and
sparc-sun-solaris2.1[01], abi_check results are clean with the
additions noted above.

Ok for mainline?

	Rainer


2015-04-02  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>

	* config/abi/post/solaris2.10/baseline_symbols.txt: Regenerate.
	* config/abi/post/solaris2.10/amd64/baseline_symbols.txt: Likewise.
	* config/abi/post/solaris2.10/sparcv9/baseline_symbols.txt: Likewise.


[-- Attachment #2: sol2-libstdc++-baseline-gcc50.patch.gz --]
[-- Type: application/octet-stream, Size: 46158 bytes --]

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]


-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

             reply	other threads:[~2015-04-08 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 13:52 Rainer Orth [this message]
     [not found] <yddpp7e68l9.fsf@CeBiTec.Uni-Bielefeld.DE>
2015-04-08 16:18 ` Jonathan Wakely
  -- strict thread matches above, loose matches on Subject: below --
2014-01-06 14:11 Rainer Orth
2014-01-06 14:40 ` Jonathan Wakely
2013-02-26 11:34 Rainer Orth
2013-02-28 13:24 ` Paolo Carlini
2013-02-28 13:29   ` Rainer Orth
2013-02-28 18:47     ` 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=yddh9sq6833.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --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).