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++/108409] std::chrono::current_zone() doesn't work on AIX
Date: Sat, 14 Jan 2023 22:05:33 +0000	[thread overview]
Message-ID: <bug-108409-4-OceCnawEXT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108409-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> We should parse the TZ env var and see if it is already an IANA name, and
> handle a few other special cases. E.g. gcc119 in the cfarm hax TZ=CUT0 which
> means a time zone named "CUT" (coordinated universal time) with a 0 offset
> from UTC. So map to UTC. More generally, "FOOn" is a time zone called "FOO"
> with a -n offset, so we could map any such string to "Etc/GMT-n"

It now works if TZ contains an IANA time zone name, or any string matching
"???0". If the systemwide TZ isn't one of those, users can define TZ for their
own programs' environment.

I don't know if that's good enough.

  parent reply	other threads:[~2023-01-14 22:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-14 19:08 [Bug libstdc++/108409] New: " redi at gcc dot gnu.org
2023-01-14 19:17 ` [Bug libstdc++/108409] " redi at gcc dot gnu.org
2023-01-14 21:59 ` cvs-commit at gcc dot gnu.org
2023-01-14 22:05 ` redi at gcc dot gnu.org [this message]
2023-01-15 13:42 ` redi at gcc dot gnu.org
2023-01-15 13:56 ` redi at gcc dot gnu.org
2023-01-15 13:58 ` redi at gcc dot gnu.org
2023-11-06 17:26 ` [Bug libstdc++/108409] std::chrono::current_zone() doesn't work on AIX or Windows mac at mcrowe dot com

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-108409-4-OceCnawEXT@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).