[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#54698: non-recursive GC marking [PATCH]
From: |
Mattias Engdegård |
Subject: |
bug#54698: non-recursive GC marking [PATCH] |
Date: |
Mon, 4 Apr 2022 16:39:58 +0200 |
4 apr. 2022 kl. 16.32 skrev Andrea Corallo <akrl@sdf.org>:
> do you have any other performance measure for cases different than the
> one mentioned?
Well, there is the usual collection of special-purpose benchmarks, and I also
timed the GC after a precise set of interactions involving scrolling through
xdisp.c and typecore.ml, as well as running magit. And ran Relint, and a few
more things I can't remember. The numbers were all largely consistent, but I
encourage you to run your fav workload.
Anything particular on your mind?
- bug#54698: non-recursive GC marking [PATCH], (continued)
- bug#54698: non-recursive GC marking [PATCH], Lars Ingebrigtsen, 2022/04/08
- bug#54698: non-recursive GC marking [PATCH], Po Lu, 2022/04/08
- bug#54698: non-recursive GC marking [PATCH], Lars Ingebrigtsen, 2022/04/08
- bug#54698: non-recursive GC marking [PATCH], Po Lu, 2022/04/08
- bug#54698: non-recursive GC marking [PATCH], Lars Ingebrigtsen, 2022/04/08
- bug#54698: non-recursive GC marking [PATCH], Phil Sainty, 2022/04/08
- bug#54698: non-recursive GC marking [PATCH], Eli Zaretskii, 2022/04/08
bug#54698: non-recursive GC marking [PATCH], Andrea Corallo, 2022/04/04
- bug#54698: non-recursive GC marking [PATCH],
Mattias Engdegård <=