public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: async: tolerate slightly shorter sleep
Date: Wed, 12 Oct 2022 12:45:22 +0100	[thread overview]
Message-ID: <CACb0b4=ckJsZf17wPQ+aeAFCGdXTnJ0NVQ5u9Ww3J8qCO+eGUw@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4nt2rOPuWhMg3po+pukQrtfeYd2uwAHtSSNOOZbj6dULw@mail.gmail.com>

On Wed, 12 Oct 2022 at 12:41, Jonathan Wakely wrote:
>
> On Thu, 23 Jun 2022 at 12:38, Alexandre Oliva via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
> >
> > On Jun 22, 2022, Alexandre Oliva <oliva@adacore.com> wrote:
> >
> > > Regstrapped on x86_64-linux-gnu, also tested with a cross to
> > > aarch64-rtems6.  Ok to install?
> >
> > The early wakeups are fixed for rtems6.1, so the same question raised at
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597102.html apply to
> > this one:
>
> Looks like I never reviewed this one, sorry.
>
> The patch to xfail this test for rtems is OK.

It's also fine if you just want to drop this patch for the same reason
as https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597105.html

(I'm just going through old patch submissions that never got acked or
nacked and this was one of them.)


  reply	other threads:[~2022-10-12 11:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  6:03 Alexandre Oliva
2022-06-23 11:36 ` Alexandre Oliva
2022-10-12 11:41   ` Jonathan Wakely
2022-10-12 11:45     ` Jonathan Wakely [this message]
2022-10-12 21:11       ` Alexandre Oliva

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='CACb0b4=ckJsZf17wPQ+aeAFCGdXTnJ0NVQ5u9Ww3J8qCO+eGUw@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --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).