From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>,
Josselin Poiret <dev@jpoiret.xyz>,
Tobias Geerinckx-Rice <me@tobias.gr>,
Simon Tournier <zimon.toutoune@gmail.com>,
Mathieu Othacehe <othacehe@gnu.org>,
Christopher Baines <mail@cbaines.net>,
61873@debbugs.gnu.org, Andrew Whatson <whatson@tailcall.au>
Subject: [bug#61873] [PATCH core-updates] gnu: libgc: Update to 8.2.2 and remove '--disable-munmap'.
Date: Tue, 28 Feb 2023 18:47:09 +0100 [thread overview]
Message-ID: <Y/4+HS0G59stzdyr@jurong> (raw)
In-Reply-To: <20230228173854.25132-1-ludo@gnu.org>
Am Tue, Feb 28, 2023 at 06:38:54PM +0100 schrieb Ludovic Courtès:
> This is another proposal for a world-rebuild change, hopefully the latest
> (I swear!). It’s quite important because it fixes a libgc bug that led
> us to build libgc with ‘--disable-munmap’, meaning it would not return
> memory to the OS:
> https://github.com/ivmai/bdwgc/issues/353
> Thanks to Andrew Whatson for tackling this and for letting me know!
>
> Given that the test suite of Guix passed and that everything in between
> went fine, I’m rather confident.
> Thoughts?
Indeed, the bug looks important to fix!
Concerning world rebuilding, I do not know if anybody did; I did not ;-)
So maybe after pushing this, we could set up jobs on the build farms to
rebuild the world twice.
Andreas
next prev parent reply other threads:[~2023-02-28 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 17:38 [bug#61873] [PATCH core-updates] gnu: libgc: Update to 8.2.2 and remove '--disable-munmap' Ludovic Courtès
2023-02-28 17:47 ` Andreas Enge [this message]
2023-03-02 14:36 ` Andreas Enge
2023-03-02 18:29 ` Josselin Poiret via Guix-patches via
2023-03-02 20:54 ` bug#61873: " Ludovic Courtès
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=Y/4+HS0G59stzdyr@jurong \
--to=andreas@enge.fr \
--cc=61873@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=whatson@tailcall.au \
--cc=zimon.toutoune@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.