bug#67141: 30.0.50; Missing element in the backtrace

[Stefan Monnier]

>> With ea7a52dbaed I added eval to 'native-comp-never-optimize-functions'
>> so this should fix the reported issue,

Thanks.

>> for mapcar I think we should prove it has really no performance
>> impact before deciding to include it as well.

Agreed.  It occurred to me that there are several places where we use
`mapcar` with a lists that's usually empty, and hence where the funcall
overhead is not necessarily negligible.

> Should this bug be closed now?

AFAIK the sample backtrace is only one among many others and the fact
that the missing element in the backtrace happened to be using `eval` is
circumstantial, so the addition of `eval` to
`native-comp-never-optimize-functions` just circumvents the problem for
`eval` but not for all the other C primitives we call directly.

IOW no, I don't think it fixes the bug :-(


        Stefan