public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] PR libstdc++/81092 add std::wstring symbols and bump library version
Date: Fri, 16 Jun 2017 14:20:00 -0000	[thread overview]
Message-ID: <20170616142048.GK2123@tucnak> (raw)
In-Reply-To: <20170614181305.GE2958@redhat.com>

On Wed, Jun 14, 2017 at 07:13:05PM +0100, Jonathan Wakely wrote:
> Target maintainers will need to regenerate the baseline symbols on
> gcc-7-branch and trunk.
> 
> I intend to commit this tomorrow to gcc-7-branch.
> 
> 

> commit 425e1d784d9085f0f8d58ef6a381cc73d564f2f5
> Author: Jonathan Wakely <jwakely@redhat.com>
> Date:   Wed Jun 14 14:06:40 2017 +0100
> 
>     PR libstdc++/81092 add std::wstring symbols and bump library version
>     
>     	PR libstdc++/81092
>     	* acinclude.m4: Bump libtool_VERSION.
>     	* config/abi/post/i386-linux-gnu/baseline_symbols.txt: Update.
>     	* config/abi/post/x86_64-linux-gnu/32/baseline_symbols.txt: Update.

Here is corresponding patch for i486 (which is just a copy of i386), ok
for gcc-7-branch?

2017-06-16  Jakub Jelinek  <jakub@redhat.com>

	PR libstdc++/81092
	* config/abi/post/i486-linux-gnu/baseline_symbols.txt: Update.

--- libstdc++-v3/config/abi/post/i486-linux-gnu/baseline_symbols.txt.jj	2017-04-20 12:18:56.748224426 +0200
+++ libstdc++-v3/config/abi/post/i486-linux-gnu/baseline_symbols.txt	2017-06-16 16:08:30.187489797 +0200
@@ -1329,6 +1329,7 @@ FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC1EP
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC1EPKwjRKS1_@@GLIBCXX_3.4
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC1ERKS1_@@GLIBCXX_3.4
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC1ERKS2_@@GLIBCXX_3.4
+FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC1ERKS2_jRKS1_@@GLIBCXX_3.4.24
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC1ERKS2_jj@@GLIBCXX_3.4
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC1ERKS2_jjRKS1_@@GLIBCXX_3.4
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC1ESt16initializer_listIwERKS1_@@GLIBCXX_3.4.11
@@ -1342,6 +1343,7 @@ FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC2EP
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC2EPKwjRKS1_@@GLIBCXX_3.4
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC2ERKS1_@@GLIBCXX_3.4
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC2ERKS2_@@GLIBCXX_3.4
+FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC2ERKS2_jRKS1_@@GLIBCXX_3.4.24
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC2ERKS2_jj@@GLIBCXX_3.4
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC2ERKS2_jjRKS1_@@GLIBCXX_3.4
 FUNC:_ZNSbIwSt11char_traitsIwESaIwEEC2ESt16initializer_listIwERKS1_@@GLIBCXX_3.4.11
@@ -4002,6 +4004,7 @@ OBJECT:0:GLIBCXX_3.4.20
 OBJECT:0:GLIBCXX_3.4.21
 OBJECT:0:GLIBCXX_3.4.22
 OBJECT:0:GLIBCXX_3.4.23
+OBJECT:0:GLIBCXX_3.4.24
 OBJECT:0:GLIBCXX_3.4.3
 OBJECT:0:GLIBCXX_3.4.4
 OBJECT:0:GLIBCXX_3.4.5


	Jakub

  parent reply	other threads:[~2017-06-16 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 18:13 Jonathan Wakely
2017-06-14 18:14 ` Jonathan Wakely
2017-06-16 14:21   ` Jakub Jelinek
2017-06-16 14:25     ` Jonathan Wakely
2017-06-19  9:19   ` Rainer Orth
2017-06-19  9:58     ` Jonathan Wakely
2017-06-16 14:20 ` Jakub Jelinek [this message]
2017-06-16 14:24   ` Jonathan Wakely
2017-06-21  8:56 ` 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=20170616142048.GK2123@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.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).