[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeat
From: |
Eli Zaretskii |
Subject: |
bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require |
Date: |
Sat, 03 Jun 2023 17:14:29 +0300 |
> Date: Sat, 3 Jun 2023 15:05:06 +0100
> From: Jimmy Wong <wyuenho@gmail.com>
> Cc: 63871-done@debbugs.gnu.org
>
> When there’s a package or a file that should not be natively compiled, there
> should be a global
> blacklist variable that controls that instead of relying on a file local
> variable in order to short circuit this
> behavior.
We decided against that. (A blacklist would unnecessarily complicate
any changes in our decisions which file to compile and which not to
compile.) We think what we have now is perfectly fine. I still don't
understand why you see a problem there. It's perhaps unexpected, but
that's all. It's a buffer users normally don't need to look into.
The alternatives are worse, sometimes much worse.
bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require, Jimmy Wong, 2023/06/03
- bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require,
Eli Zaretskii <=
- bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require, Jimmy Wong, 2023/06/03
- bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require, Eli Zaretskii, 2023/06/03
- bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require, Jimmy Wong, 2023/06/03
- bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require, Eli Zaretskii, 2023/06/03
- bug#63871: 29.0.91; JIT native comp triggered to compile loaddefs repeatedly on require, Jimmy Wong, 2023/06/03