public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113450] [14 Regression] std/format/functions/format.cc FAILs Date: Mon, 26 Feb 2024 13:40:23 +0000 [thread overview] Message-ID: <bug-113450-4-W4GnKB1OZ8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113450-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113450 --- Comment #19 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- I'm talking with Oracle Solaris Engineering and they're amenable to making the int8_t change from char to signed char. To assess the possible impact, the plan is to compare the public symbols of C++ libraries delivered with Solaris now and after a rebuild with <sys/int_types.h> changed. Are there other important issues to consider with such a change?
prev parent reply other threads:[~2024-02-26 13:40 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-17 15:06 [Bug libstdc++/113450] New: " ro at gcc dot gnu.org 2024-01-17 15:07 ` [Bug libstdc++/113450] " ro at gcc dot gnu.org 2024-01-17 21:32 ` [Bug libstdc++/113450] [14 Regression] " redi at gcc dot gnu.org 2024-01-18 10:06 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-01-18 12:54 ` cvs-commit at gcc dot gnu.org 2024-01-18 12:58 ` redi at gcc dot gnu.org 2024-01-18 21:03 ` cvs-commit at gcc dot gnu.org 2024-01-19 8:47 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-14 16:46 ` redi at gcc dot gnu.org 2024-02-14 16:51 ` jakub at gcc dot gnu.org 2024-02-14 16:54 ` redi at gcc dot gnu.org 2024-02-14 17:00 ` jakub at gcc dot gnu.org 2024-02-20 16:09 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-20 16:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-20 16:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-21 9:56 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-21 11:33 ` redi at gcc dot gnu.org 2024-02-21 13:34 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-21 16:42 ` jsm28 at gcc dot gnu.org 2024-02-22 8:51 ` ro at CeBiTec dot Uni-Bielefeld.DE 2024-02-26 13:40 ` ro at CeBiTec dot Uni-Bielefeld.DE [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=bug-113450-4-W4GnKB1OZ8@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).