[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: last_marked array is now ifdef'ed away
From: |
Stefan Kangas |
Subject: |
Re: last_marked array is now ifdef'ed away |
Date: |
Sat, 14 Sep 2024 15:50:03 -0700 |
Eli Zaretskii <eliz@gnu.org> writes:
> I'm quite confident that I want this be turned on again.
Since this affects performance by quite a bit (4.5-6.5 %, reportedly),
how about the suggestion to "hitch it to another existing config option
like ENABLE_CHECKING, or even make this an independent config option"?
- Re: last_marked array is now ifdef'ed away, (continued)
- Re: last_marked array is now ifdef'ed away, Mattias Engdegård, 2024/09/13
- Re: last_marked array is now ifdef'ed away, Eli Zaretskii, 2024/09/13
- Re: last_marked array is now ifdef'ed away, Mattias Engdegård, 2024/09/14
- Re: last_marked array is now ifdef'ed away, Eli Zaretskii, 2024/09/14
- Re: last_marked array is now ifdef'ed away, Mattias Engdegård, 2024/09/14
- Re: last_marked array is now ifdef'ed away, Eli Zaretskii, 2024/09/15
- Re: last_marked array is now ifdef'ed away, Mattias Engdegård, 2024/09/15
- Re: last_marked array is now ifdef'ed away, Eli Zaretskii, 2024/09/15
- Re: last_marked array is now ifdef'ed away, Mattias Engdegård, 2024/09/17
- Re: last_marked array is now ifdef'ed away, Eli Zaretskii, 2024/09/17
- Re: last_marked array is now ifdef'ed away,
Stefan Kangas <=
- Re: last_marked array is now ifdef'ed away, Eli Zaretskii, 2024/09/15
- Re: last_marked array is now ifdef'ed away, Andrea Corallo, 2024/09/16