[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-o
From: |
Andrea Corallo |
Subject: |
bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil) |
Date: |
Sat, 09 Mar 2024 16:41:02 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> (defalias 're-search-forward-ifpmod (symbol-function 're-search-forward)
>>> ...)
> [...]
>> Stefan, can you help maybe? Gabriele then does this:
> [...]
>> and we have found that this causes weird errors because at least some
>> definitions, like `forward-paragraph', call `re-search-forward-ifpmod'
>> afterwards. This seems to happen only when using a native compiled
>
> Sounds like a problem in the code that installs trampolines.
>
> Andrea?
>
> If we look at `fset`, the C code does:
>
> if (!NILP (Vnative_comp_enable_subr_trampolines)
> && SUBRP (function)
> && !SUBR_NATIVE_COMPILEDP (function))
> CALLN (Ffuncall, Qcomp_subr_trampoline_install, symbol);
>
> so indeed if the SUBR_NATIVE_COMPILEDP function is stored in another
> symbol, we will still call Qcomp_subr_trampoline_install, even tho it's
> a case where it should not be necessary, and I suspect this can lead to
> the kind of problems mentioned above, if we do something like
>
> (defalias 'foo (symbol-function 'bar))
> (fset 'foo <something-else>)
>
> where native calls to `bar` could end up redirected to the definition of
> `foo` :-(
Here I'm,
mmmhh, I'm really not sure why calling Qcomp_subr_trampoline_install
should be problematic. I'll look at it, but this week I'm on holiday so
might take a bit more :)
Bests
Andrea
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Gabriele Nicolardi, 2024/03/05
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Michael Heerdegen, 2024/03/05
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Gabriele Nicolardi, 2024/03/06
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Michael Heerdegen, 2024/03/06
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Michael Heerdegen, 2024/03/07
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Gabriele Nicolardi, 2024/03/07
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Michael Heerdegen, 2024/03/08
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Stefan Monnier, 2024/03/09
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil),
Andrea Corallo <=
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Stefan Monnier, 2024/03/09
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Andrea Corallo, 2024/03/15
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Stefan Monnier, 2024/03/15
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Gabriele Nicolardi, 2024/03/15
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Andrea Corallo, 2024/03/15
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Gabriele Nicolardi, 2024/03/17
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Stefan Monnier, 2024/03/15
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Gabriele Nicolardi, 2024/03/17
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Andrea Corallo, 2024/03/18
- bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil), Gabriele Nicolardi, 2024/03/18