public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crrodriguez at opensuse dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/26540] [linux-only] nanosleep should call the syscall of the same name, not the posix version
Date: Thu, 27 Aug 2020 13:05:42 +0000	[thread overview]
Message-ID: <bug-26540-131-xEJWLmzysH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26540-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26540

--- Comment #7 from Cristian Rodríguez <crrodriguez at opensuse dot org> ---
(In reply to Adhemerval Zanella from comment #4)

> So it does not really matter which clock you use.  I will follow with
> man-pages mantainer to update the glibc documentation.


Thanks for digging further, indeed.. the clock only matter is TIMER_ABSTIME is
set. (thanks $deity)

static void __hrtimer_init(struct hrtimer *timer, clockid_t clock_id,
                           enum hrtimer_mode mode)
...

if (clock_id == CLOCK_REALTIME && mode != HRTIMER_MODE_ABS)
                clock_id = CLOCK_MONOTONIC;

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2020-08-27 13:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 19:46 [Bug string/26540] New: " crrodriguez at opensuse dot org
2020-08-26 21:27 ` [Bug string/26540] " adhemerval.zanella at linaro dot org
2020-08-26 22:01 ` crrodriguez at opensuse dot org
2020-08-26 22:21 ` crrodriguez at opensuse dot org
2020-08-26 22:55 ` adhemerval.zanella at linaro dot org
2020-08-27  8:42 ` fweimer at redhat dot com
2020-08-27 10:49 ` adhemerval.zanella at linaro dot org
2020-08-27 13:05 ` crrodriguez at opensuse dot 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-26540-131-xEJWLmzysH@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).