public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
	Florian Weimer <fweimer@redhat.com>,
	'GNU C Library' <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Improve performance of IO locks
Date: Wed, 17 Aug 2022 13:53:49 +0200	[thread overview]
Message-ID: <YvzWzc0XP3sREol3@wildebeest.org> (raw)
In-Reply-To: <m31qtg2ras.fsf@fitzsim.org>

Hi Tom.

On Tue, Aug 16, 2022 at 10:31:39AM -0400, Thomas Fitzsimmons wrote:
> Before setting this up, I checked the system's package list.  This
> builder is running Debian unstable, without unattended upgrades, so some
> of the toolchain packages were out-of-date.
> 
> I did an upgrade (388 packages) and the issue seems to have disappeared,
> so this was likely a toolchain bug that has since been fixed.  I have
> the list of old and new package versions if anyone's interested.
> 
> Anyway, I think glibc-debian-ppc64 builds will succeed now.

It did!
https://builder.sourceware.org/buildbot/#builders/128/builds/182

Thanks,

Mark

      reply	other threads:[~2022-08-17 13:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 16:32 Wilco Dijkstra
2022-08-01 11:06 ` Wilco Dijkstra
2022-08-07 12:51   ` Cristian Rodríguez
2022-08-15 22:27   ` Mark Wielaard
2022-08-16  3:07     ` Thomas Fitzsimmons
2022-08-16  7:31       ` Florian Weimer
2022-08-16 10:00         ` Mark Wielaard
2022-08-16 10:08           ` Florian Weimer
2022-08-17 13:45             ` Mark Wielaard
2022-08-22 10:25               ` Florian Weimer
2022-08-22 14:58                 ` Frank Ch. Eigler
2022-08-16 11:19           ` Andreas Schwab
2022-08-16 10:24         ` Wilco Dijkstra
2022-08-16 13:18           ` Thomas Fitzsimmons
2022-08-16 14:31             ` Thomas Fitzsimmons
2022-08-17 11:53               ` Mark Wielaard [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=YvzWzc0XP3sREol3@wildebeest.org \
    --to=mark@klomp.org \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=fitzsim@fitzsim.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).