public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/59177] steady_clock::now() and system_clock::now do not use the vdso (and are therefore very slow) Date: Mon, 18 Nov 2013 19:25:00 -0000 [thread overview] Message-ID: <bug-59177-4-d6Bghxu9HL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59177-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59177 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The default for --enable-libstdcxx-time is =auto, which should be the right thing: gnu* | linux* | kfreebsd*-gnu | knetbsd*-gnu) AC_MSG_CHECKING([for at least GNU libc 2.17]) AC_TRY_COMPILE( [#include <features.h>], [ #if ! __GLIBC_PREREQ(2, 17) #error #endif ], [glibcxx_glibc217=yes], [glibcxx_glibc217=no]) AC_MSG_RESULT($glibcxx_glibc217) if test x"$glibcxx_glibc217" = x"yes"; then ac_has_clock_monotonic=yes ac_has_clock_realtime=yes fi ac_has_nanosleep=yes ac_has_sched_yield=yes My trunk build on Fedora 19 today has: /* Defined if clock_gettime syscall has monotonic and realtime clock support. */ /* #undef _GLIBCXX_USE_CLOCK_GETTIME_SYSCALL */ /* Defined if clock_gettime has monotonic clock support. */ #define _GLIBCXX_USE_CLOCK_MONOTONIC 1 /* Defined if clock_gettime has realtime clock support. */ #define _GLIBCXX_USE_CLOCK_REALTIME 1 and there are two clock_gettime calls in libstdc++.so.6 as they should be.
next prev parent reply other threads:[~2013-11-18 19:25 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-18 18:23 [Bug libstdc++/59177] New: " luto at mit dot edu 2013-11-18 18:38 ` [Bug libstdc++/59177] " paolo.carlini at oracle dot com 2013-11-18 18:46 ` jakub at gcc dot gnu.org 2013-11-18 19:15 ` luto at mit dot edu 2013-11-18 19:25 ` jakub at gcc dot gnu.org [this message] 2013-11-18 19:46 ` luto at mit dot edu 2013-11-18 19:50 ` jakub at gcc dot gnu.org 2013-11-18 19:53 ` luto at mit dot edu 2013-11-18 19:58 ` jakub at gcc dot gnu.org 2013-11-18 20:03 ` luto at mit dot edu 2013-11-18 20:17 ` paolo.carlini at oracle dot com 2013-11-19 0:15 ` redi at gcc dot gnu.org 2013-11-19 0:45 ` luto at mit dot edu
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-59177-4-d6Bghxu9HL@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).