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++/63400] [C++11]precision of std::chrono::high_resolution_clock
Date: Mon, 29 Sep 2014 09:33:00 -0000 [thread overview]
Message-ID: <bug-63400-4-AVOummfm2X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63400-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63400
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |mingw-w64
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Which of macros are defined on mingw-w64?
Preprocessing this should tell you
#include <chrono>
#ifdef _GLIBCXX_USE_CLOCK_REALTIME
#ifdef _GLIBCXX_USE_CLOCK_GETTIME_SYSCALL
#warning system_clock using syscall(SYS_clock_gettime, CLOCK_REALTIME, &tp);
#else
#warning system_clock using clock_gettime(CLOCK_REALTIME, &tp);
#endif
#elif defined(_GLIBCXX_USE_GETTIMEOFDAY)
#warning system_clock using gettimeofday(&tv, 0);
#else
#warning system_clock using std::time(0);
#endif
#ifdef _GLIBCXX_USE_CLOCK_MONOTONIC
#ifdef _GLIBCXX_USE_CLOCK_GETTIME_SYSCALL
#warning steady_clock using syscall(SYS_clock_gettime, CLOCK_MONOTONIC, &tp);
#else
#warning steady_clock using clock_gettime(CLOCK_MONOTONIC, &tp);
#endif
#else
#warning steady_clock using time_point(system_clock::now().time_since_epoch());
#endif
next parent reply other threads:[~2014-09-29 9:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-63400-4@http.gcc.gnu.org/bugzilla/>
2014-09-29 9:33 ` redi at gcc dot gnu.org [this message]
2014-09-29 17:18 ` redi at gcc dot gnu.org
2014-09-29 21:00 ` frankhb1989 at gmail dot com
2014-09-29 21:03 ` frankhb1989 at gmail dot com
2014-09-30 10:36 ` redi at gcc dot gnu.org
2022-07-14 18:17 ` redi at gcc dot gnu.org
2022-07-14 18:19 ` redi at gcc dot gnu.org
2022-07-15 10:37 ` redi at gcc dot gnu.org
2024-03-08 10:21 ` redi at gcc dot gnu.org
2024-03-08 10:21 ` redi at gcc dot gnu.org
2024-03-08 11:41 ` redi at gcc dot gnu.org
2024-03-08 13:47 ` vz-gcc at zeitlins dot org
2024-03-08 14:37 ` redi at gcc dot gnu.org
2024-03-08 14:38 ` redi at gcc dot gnu.org
2024-03-08 15:03 ` vz-gcc at zeitlins dot 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-63400-4-AVOummfm2X@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).