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: Thu, 18 Jan 2024 10:06:24 +0000	[thread overview]
Message-ID: <bug-113450-4-dAMUyBZVWy@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 #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> I assume that int8_t is char on Solaris, rather than signed char?

Indeed.  AFAIK char being signed goes back to SysVr4 at least (and has
bitten us several times already, especially over in LLVM).

> Formatting a char behaves differently from signed char, and other integral
> types.
>
> I think this will fix it:
[...]
> That causes the lambda to use signed char instead of char, and that is
> formatted as an integer not a character.

It does indeed.  Tested on both i386-pc-solaris2.11 and
sparc-sun-solaris2.11 for good measure.  Thanks!

  parent reply	other threads:[~2024-01-18 10:06 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 [this message]
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

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-dAMUyBZVWy@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: 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).