public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107081] ctime fct used twice in printf
Date: Thu, 29 Sep 2022 01:39:09 +0000 [thread overview]
Message-ID: <bug-107081-4-coPsWvCNOj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107081-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107081
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
ctime returns the same pointer no matter what. It
https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1548.pdf
The ctime function returns the pointer returned by the asctime function with
that
broken-down time as argument.
"Execution of
any of the functions that return a pointer to one of these object types may
overwrite the
information in any object of the same type pointed to by the value returned
from any
previous call to any of them and the functions are not required to avoid data
races.
"
prev parent reply other threads:[~2022-09-29 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 1:32 [Bug c/107081] New: " francois.hebert001 at videotron dot ca
2022-09-29 1:39 ` pinskia at gcc dot gnu.org [this message]
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-107081-4-coPsWvCNOj@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).