public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113450] New: std/format/functions/format.cc FAILs Date: Wed, 17 Jan 2024 15:06:56 +0000 [thread overview] Message-ID: <bug-113450-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113450 Bug ID: 113450 Summary: std/format/functions/format.cc FAILs Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: redi at gcc dot gnu.org Target Milestone: --- Target: *-*-solaris2.11 The new std/format/functions/format.cc test FAILs on Solaris/SPARC and x86, both 32 and 64-bit: +FAIL: std/format/functions/format.cc -std=gnu++20 execution test +FAIL: std/format/functions/format.cc -std=gnu++26 execution test It shows an assertion failure /vol/gcc/src/hg/master/local/libstdc++-v3/testsuite/std/format/functions/format.cc:360: test_minmax()::<lambda(T, U)> [with T = char; U = unsigned char]: Assertion 's == "-1" + zeros' failed. #3 0x00027554 in operator()<char> (__closure=<optimized out>) at /vol/gcc/src/hg/master/local/libstdc++-v3/testsuite/std/format/functions/format.cc:360 360 VERIFY( s == "-1" + zeros ); (gdb) p s $1 = { _M_dataplus = {<std::allocator<char>> = {<std::__new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0xffbfe808 "10000000"}, _M_string_length = 8, { _M_local_buf = "10000000\000\000\000\035\377\277\350\030", _M_allocated_capacity = 825241648}}
next reply other threads:[~2024-01-17 15:06 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-17 15:06 ro at gcc dot gnu.org [this message] 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
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@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).