From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Alexandre Oliva <oliva@adacore.com>
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: Thu, 23 Jun 2022 09:27:44 +0200 [thread overview]
Message-ID: <e5340839-0fb1-4c3c-5a2f-44dfae57b20a@embedded-brains.de> (raw)
In-Reply-To: <c4f60059-3b25-7455-8834-e0078389c030@embedded-brains.de>
On 23/06/2022 08:44, Sebastian Huber wrote:
> On 23/06/2022 02:19, Alexandre Oliva wrote:
>> 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.
>
> I already created a ticket for this and work on it:
>
> http://devel.rtems.org/ticket/4669
This problem should be fixed now in the RTEMS master branch. I had to
adjust the test case so that it works in a system with only one processor:
while (!sleeping)
{
// Wait for the thread to start sleeping.
std::this_thread::yield();
}
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2022-06-23 7:27 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
2022-06-23 6:44 ` Sebastian Huber
2022-06-23 7:27 ` Sebastian Huber [this message]
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=e5340839-0fb1-4c3c-5a2f-44dfae57b20a@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=devel@rtems.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=oliva@adacore.com \
/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).