bug#67005: 30.0.50; improve nadivce/comp/trampoline handling

[Stefan Monnier]

>> Shouldn't we implement that optimization for calls to
>> native-compiled functions, tho?  At least for the case where that
>> function is defined in the same file as the call?
>
> We could, we'd need a "link table" for each file.

Hmm... that's right.

> Note that this would make the backtrace even more sparse :)

You mean that it would push up the urgency to fix that bug?
Maybe fixing that bug could be used to simplify the trampolines
(because the symbol holding the function that we're calling would then
be available, so the trampoline could use it, making it possible to use
a fixed set of trampolines (one per calling convention) rather than one
per function).


        Stefan