public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107817] std/format/functions/format.cc etc. FAIL
Date: Tue, 22 Nov 2022 21:35:30 +0000 [thread overview]
Message-ID: <bug-107817-4-8uW6JtQ0cY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107817-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107817
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Native configuration is sparc-sun-solaris2.11
=== libstdc++ tests ===
Schedule of variations:
unix
Running target unix
Running
/export/home/jwakely/src/gcc/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...
PASS: std/format/arguments/args.cc (test for excess errors)
PASS: std/format/arguments/args.cc execution test
PASS: std/format/error.cc (test for excess errors)
PASS: std/format/error.cc execution test
PASS: std/format/formatter/concept.cc (test for excess errors)
PASS: std/format/formatter/requirements.cc (test for excess errors)
PASS: std/format/formatter/requirements.cc execution test
PASS: std/format/functions/format.cc (test for excess errors)
PASS: std/format/functions/format.cc execution test
PASS: std/format/functions/format_to_n.cc (test for excess errors)
PASS: std/format/functions/format_to_n.cc execution test
PASS: std/format/functions/size.cc (test for excess errors)
PASS: std/format/functions/size.cc execution test
PASS: std/format/functions/vformat_to.cc (test for excess errors)
PASS: std/format/functions/vformat_to.cc execution test
PASS: std/format/parse_ctx.cc (test for excess errors)
PASS: std/format/parse_ctx.cc execution test
PASS: std/format/string.cc (test for excess errors)
PASS: std/format/string.cc execution test
PASS: std/format/string_neg.cc (test for errors, line )
PASS: std/format/string_neg.cc (test for excess errors)
=== libstdc++ Summary ===
# of expected passes 21
next prev parent reply other threads:[~2022-11-22 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 14:05 [Bug libstdc++/107817] New: " ro at gcc dot gnu.org
2022-11-22 14:05 ` [Bug libstdc++/107817] " ro at gcc dot gnu.org
2022-11-22 17:12 ` redi at gcc dot gnu.org
2022-11-22 17:16 ` redi at gcc dot gnu.org
2022-11-22 17:54 ` cvs-commit at gcc dot gnu.org
2022-11-22 18:12 ` redi at gcc dot gnu.org
2022-11-22 21:35 ` redi at gcc dot gnu.org [this message]
2022-11-24 8:59 ` 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-107817-4-8uW6JtQ0cY@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).