public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luto at mit dot edu" <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:15:00 -0000 [thread overview] Message-ID: <bug-59177-4-BwEQc5i4oI@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 #3 from Andy Lutomirski <luto at mit dot edu> --- I can't get gcc trunk to build right now, but I just distcleaned and rebuilt the 4.8 branch truck on Fedora 19, which has glibc-2.17-19.fc19.x86_64. It defines _GLIBCXX_USE_CLOCK_GETTIME_SYSCALL. This happens because: configure:19349: checking for clock_gettime, nanosleep and sched_yield configure:19378: result: no I think that the underlying problem is that --enable-libstdcxx-time defaults to "no". Shouldn't it default to "yes" (and hence run the fancy configure checks)? Configuring with ./configure --enable-libstdcxx-time does the right thing.
next prev parent reply other threads:[~2013-11-18 19:15 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 [this message] 2013-11-18 19:25 ` jakub at gcc dot gnu.org 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-BwEQc5i4oI@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).