From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] libstdc++: Update Solaris baselines for GCC 12.1
Date: Fri, 29 Apr 2022 12:32:08 +0200 [thread overview]
Message-ID: <ydd7d78ji3b.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <CACb0b4=V1bK+wMbvjsBBvqPYu=NF5nYzunaxigfO56vGR5jjWw@mail.gmail.com> (Jonathan Wakely's message of "Fri, 29 Apr 2022 09:28:36 +0100")
Jonathan Wakely <jwakely@redhat.com> writes:
> On Thu, 28 Apr 2022 at 22:40, Rainer Orth wrote:
>>
>> The following patch updates the Solaris baselines for GCC 12.1.
>>
>> Tested on i386-pc-solaris2.11 and sparc-sun-solaris2.11 (Solaris 11.3
>> and 11.4 in each case).
>>
>> The only (expected) difference between the 11.3 and 11.4 versions is
>>
>> --- baseline_symbols.txt.s113s 2022-04-28 10:37:11.464068450 +0000
>> +++ baseline_symbols.txt.s114s 2022-04-27 16:54:31.995636805 +0000
>> @@ -4070,3 +4070,3 @@
>> -FUNC:_ZSt10from_charsPKcS0_RdSt12chars_format@@GLIBCXX_3.4.30
>> -FUNC:_ZSt10from_charsPKcS0_ReSt12chars_format@@GLIBCXX_3.4.30
>> -FUNC:_ZSt10from_charsPKcS0_RfSt12chars_format@@GLIBCXX_3.4.30
>> +FUNC:_ZSt10from_charsPKcS0_RdSt12chars_format@@GLIBCXX_3.4.29
>> +FUNC:_ZSt10from_charsPKcS0_ReSt12chars_format@@GLIBCXX_3.4.29
>> +FUNC:_ZSt10from_charsPKcS0_RfSt12chars_format@@GLIBCXX_3.4.29
>>
>> which is handled by the fix for PR libstdc++/103407. I'm using the 11.4
>> version here.
>>
>> Ok for master and gcc-12 branch?
>
> OK, thanks.
Thanks. But doesn't the gcc-12 branch require RM approval at the
moment? Jakub?
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2022-04-29 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 21:39 Rainer Orth
2022-04-29 8:28 ` Jonathan Wakely
2022-04-29 10:32 ` Rainer Orth [this message]
2022-04-29 10:33 ` Jakub Jelinek
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=ydd7d78ji3b.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--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).