public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108530] New: [13 regression] std/time/tzdb/1.cc fails after r13-5168-g559993b85744ae
Date: Tue, 24 Jan 2023 19:46:52 +0000 [thread overview]
Message-ID: <bug-108530-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530
Bug ID: 108530
Summary: [13 regression] std/time/tzdb/1.cc fails after
r13-5168-g559993b85744ae
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:559993b85744ae09d33eedb1cb062392ac482f94, r13-5168-g559993b85744ae
This started failing on one of our older (power 7 BE) servers after this
commit. Does the change maybe require something not supported here (an older
SUSE distro)?
make -k check RUNTESTFLAGS="conformance.exp=std/time/tzdb/1.cc"
FAIL: std/time/tzdb/1.cc execution test
# of expected passes 1
# of unexpected failures 1
terminate called after throwing an instance of 'std::runtime_error'
what(): tzdb: cannot determine current zone
FAIL: std/time/tzdb/1.cc execution test
std/time/zoned_time/custom.cc also fails now with the same error.
commit 559993b85744ae09d33eedb1cb062392ac482f94
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Sat Jan 14 13:33:58 2023 +0000
libstdc++: Embed a static copy of tzdata.zi
next reply other threads:[~2023-01-24 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 19:46 seurer at gcc dot gnu.org [this message]
2023-01-24 20:16 ` [Bug libstdc++/108530] " redi at gcc dot gnu.org
2023-01-24 21:20 ` seurer at gcc dot gnu.org
2023-01-24 23:21 ` redi at gcc dot gnu.org
2023-01-24 23:42 ` redi at gcc dot gnu.org
2023-01-24 23:51 ` cvs-commit at gcc dot gnu.org
2023-01-24 23:53 ` redi at gcc dot gnu.org
2023-01-25 7:37 ` rguenth at gcc dot gnu.org
2023-01-26 13:38 ` 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-108530-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: 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).