[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MPS GC and its implications
From: |
Helmut Eller |
Subject: |
Re: MPS GC and its implications |
Date: |
Fri, 03 May 2024 14:28:13 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
>> Memory barriers could be used for synchronization. When the mutator
>> hits a barrier, it executes the signal handler. The signal handler asks
>> the collector what to do. Essentially synchronizing those two.
>
> If this happens, I should have seen GDB intercept the exception and
> kick in. But it doesn't. (It also would have slowed the program
> quite a lot, I think.)
Don't call igc--collect and do something to generate enough garbage.
Then you'll see it.
- Re: MPS GC and its implications, (continued)
- Re: MPS GC and its implications, Andrea Corallo, 2024/05/02
- Re: MPS GC and its implications, Gerd Möllmann, 2024/05/03
- Re: MPS GC and its implications, Eli Zaretskii, 2024/05/03
- Re: MPS GC and its implications, Helmut Eller, 2024/05/03
- Re: MPS GC and its implications, Eli Zaretskii, 2024/05/03
- Re: MPS GC and its implications, Gerd Möllmann, 2024/05/03
- Re: MPS GC and its implications, Eli Zaretskii, 2024/05/03
- Re: MPS GC and its implications, Gerd Möllmann, 2024/05/03
- Re: MPS GC and its implications, Andrea Corallo, 2024/05/03
- Re: MPS GC and its implications, Gerd Möllmann, 2024/05/03
- Re: MPS GC and its implications,
Helmut Eller <=
- Re: MPS GC and its implications, Eli Zaretskii, 2024/05/03
- Re: MPS GC and its implications, Helmut Eller, 2024/05/03
- Re: MPS GC and its implications, Eli Zaretskii, 2024/05/03
- Re: MPS GC and its implications, Eli Zaretskii, 2024/05/03
- Re: MPS GC and its implications, Helmut Eller, 2024/05/04
- Re: MPS GC and its implications, Eli Zaretskii, 2024/05/04
- Re: MPS GC and its implications, Gerd Möllmann, 2024/05/04
- Re: MPS GC and its implications, Eli Zaretskii, 2024/05/04
- Re: MPS GC and its implications, Helmut Eller, 2024/05/04
- Re: MPS GC and its implications, Mattias Engdegård, 2024/05/04