public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/14438] clock_gettime CLOCK_THREAD_CPUTIME_ID doesn't delegate to vsyscall
Date: Fri, 10 May 2013 13:02:00 -0000	[thread overview]
Message-ID: <bug-14438-131-6Zy4geMZaP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14438-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14438

Siddhesh Poyarekar <siddhesh at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siddhesh at redhat dot com

--- Comment #1 from Siddhesh Poyarekar <siddhesh at redhat dot com> 2013-05-10 13:02:28 UTC ---
clock_gettime always calls __vdso_clock_gettime on x86_64.  What are you
testing on?

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  reply	other threads:[~2013-05-10 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 19:03 [Bug libc/14438] New: " arun@sharma-home.net
2013-05-10 13:02 ` siddhesh at redhat dot com [this message]
2013-05-10 14:09 ` [Bug libc/14438] " arun@sharma-home.net
2013-05-16  6:48 ` siddhesh at redhat dot com
2013-07-26 18:24 ` neleai at seznam dot cz
2013-07-26 18:37 ` arun@sharma-home.net
2013-07-27  2:45 ` siddhesh at redhat dot com
2013-10-04 15:53 ` arun@sharma-home.net
2014-06-17 18:47 ` fweimer at redhat dot com

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-14438-131-6Zy4geMZaP@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).