public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103407] [12 regression] abi_check FAILs on Solaris Date: Fri, 29 Apr 2022 11:50:00 +0000 [thread overview] Message-ID: <bug-103407-4-axIzyfRbyR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103407-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103407 --- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Rainer Orth <ro@gcc.gnu.org>: https://gcc.gnu.org/g:8c465ddd619bbb2949bc2bc31629c2a826a7c437 commit r13-39-g8c465ddd619bbb2949bc2bc31629c2a826a7c437 Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> Date: Fri Apr 29 13:44:49 2022 +0200 libstdc++: Update Solaris baselines for GCC 12.1 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. 2022-04-27 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> libstdc++-v3: * config/abi/post/i386-solaris/baseline_symbols.txt: Regenerate. * config/abi/post/i386-solaris/amd64/baseline_symbols.txt: Likewise. * config/abi/post/sparc-solaris/baseline_symbols.txt: Likewise. * config/abi/post/sparc-solaris/sparcv9/baseline_symbols.txt: Likewise.
next prev parent reply other threads:[~2022-04-29 11:50 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-24 11:58 [Bug libstdc++/103407] New: " ro at gcc dot gnu.org 2021-11-24 11:59 ` [Bug libstdc++/103407] " ro at gcc dot gnu.org 2021-11-24 12:05 ` rguenth at gcc dot gnu.org 2021-11-24 12:36 ` redi at gcc dot gnu.org 2021-11-25 1:05 ` pinskia at gcc dot gnu.org 2022-02-22 17:44 ` redi at gcc dot gnu.org 2022-02-23 15:57 ` redi at gcc dot gnu.org 2022-02-23 16:41 ` redi at gcc dot gnu.org 2022-02-23 16:53 ` redi at gcc dot gnu.org 2022-02-23 21:02 ` ro at gcc dot gnu.org 2022-02-24 0:58 ` redi at gcc dot gnu.org 2022-02-24 9:41 ` redi at gcc dot gnu.org 2022-02-28 14:22 ` ro at CeBiTec dot Uni-Bielefeld.DE 2022-03-10 16:16 ` redi at gcc dot gnu.org 2022-03-16 17:34 ` redi at gcc dot gnu.org 2022-03-16 21:17 ` cvs-commit at gcc dot gnu.org 2022-03-18 12:43 ` redi at gcc dot gnu.org 2022-04-29 11:50 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-29 12:02 ` cvs-commit at gcc dot gnu.org
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=bug-103407-4-axIzyfRbyR@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).