public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@adacore.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org, RTEMS <devel@rtems.org>
Subject: Re: [PATCH] libstdc++: 60241.cc: tolerate slightly shorter aggregate sleep
Date: Wed, 22 Jun 2022 21:19:53 -0300	[thread overview]
Message-ID: <orpmj06xjq.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <695d0ddd-35a9-86de-7ce2-4ba64c47379e@embedded-brains.de> (Sebastian Huber's message of "Wed, 22 Jun 2022 10:55:27 +0200")

On Jun 22, 2022, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote:

> The clock_nanosleep() uses the coarse resolution which may give a time
> before now().

Uhh, sorry, hit send too early.

I also meant to ask whether you'd like me to file an RTEMS ticket about
this issue.

-- 
Alexandre Oliva, happy hacker                https://FSFLA.org/blogs/lxo/
   Free Software Activist                       GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>

  parent reply	other threads:[~2022-06-23  0:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  6:01 Alexandre Oliva
2022-06-22  6:22 ` Sebastian Huber
2022-06-22  8:55   ` Sebastian Huber
2022-06-23  0:15     ` Alexandre Oliva
2022-06-23  0:19     ` Alexandre Oliva [this message]
2022-06-23  6:44       ` Sebastian Huber
2022-06-23  7:27         ` Sebastian Huber
2022-06-23 11:33           ` Alexandre Oliva
2022-06-23 11:37             ` Sebastian Huber

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=orpmj06xjq.fsf@lxoliva.fsfla.org \
    --to=oliva@adacore.com \
    --cc=devel@rtems.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=sebastian.huber@embedded-brains.de \
    /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).