public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "urbanjost at comcast dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/98507] New: timezone is incorrect on last day of year for "TZ" hours Date: Mon, 04 Jan 2021 02:25:02 +0000 [thread overview] Message-ID: <bug-98507-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98507 Bug ID: 98507 Summary: timezone is incorrect on last day of year for "TZ" hours Product: gcc Version: 8.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: urbanjost at comcast dot net Target Milestone: --- Created attachment 49870 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49870&action=edit call date_and_time and print timezone On the last day of the year if your timezone is not GMT the timezone value returned by the intrinsic DATE_AND_TIME is incorrect until the local date is the first of the year. That is, from 9PM till midnight on the 2020-12-31 a huge timezone value was returned that was actually a year off in minutes. On a Red Hat 8 machine this can be duplicate by setting the system time to 2200 (10PM) on 2020-12-31. date /home/urbanjs/venus/V600/bin/Linux_gfortran/bug date 123122002020.00 /home/urbanjs/venus/V600/bin/Linux_gfortran/bug exit Sun Jan 3 21:07:57 EST 2021 2021 1 3 -300 21 7 57 208 -0500 2021 1 3 -300 21 7 57 208 Thu Dec 31 22:00:00 EST 2020 2020 12 31***** 22 0 0 20 +8779 2020 12 31***** 22 0 0 20 Thu Dec 31 22:00:00 EST 2020 2020 12 31 526740 22 0 0 13 +8779 2020 12 31 526740 22 0 0 13 So in the EST timezone it is only incorrect during the last five hours of the year.
next reply other threads:[~2021-01-04 2:25 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-04 2:25 urbanjost at comcast dot net [this message] 2021-01-05 21:26 ` [Bug libfortran/98507] " anlauf at gcc dot gnu.org 2021-12-16 9:58 ` fxcoudert at gcc dot gnu.org 2021-12-16 16:50 ` fxcoudert at gcc dot gnu.org 2021-12-16 17:29 ` urbanjost at comcast dot net 2021-12-17 7:45 ` jb 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-98507-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).