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] [13 regression] std/time/tzdb/1.cc fails after r13-5168-g559993b85744ae
Date: Tue, 24 Jan 2023 21:20:14 +0000	[thread overview]
Message-ID: <bug-108530-4-GRNdEn34Rq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108530-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108530

--- Comment #2 from seurer at gcc dot gnu.org ---
Yes it is a regular file.

With the previous commit it wasn't UNSUPPORTED and worked just fine:

g:ff6c7617102df365918402c6ccc8e497c47dbe60, r13-5167-gff6c7617102df3
make  -k check RUNTESTFLAGS="conformance.exp=std/time/tzdb/1.cc"
# of expected passes            2


This is quite an old system (it's soon to be retired) and I don't see the issue
elsewhere.

  parent reply	other threads:[~2023-01-24 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 19:46 [Bug libstdc++/108530] New: " seurer at gcc dot gnu.org
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 [this message]
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-GRNdEn34Rq@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).