Seperate bytecode stack for Emacs

What's the context? should we expect faster runtime? by how much?

Good questions. Answered in the change log of the commit. Which is linked. Edit except for the "how much", which I guesstimate in the mi one digit to the low two digit percents.

Not saying anything bad about the contribution, but on the post which only includes a link and a not so informative title. Personally I think it's a low effort post; a sentence or two could be added; help focus attention and save readers time. I'm also surprised there are no benchmarks. I lurk enough time in the mailing lists to see no core contribution moves forward without benchmarks, e.g. see TimSort (python) algorithm being introduced to Emacs thread.

I see where you are coming from. What confuses me is that I find no discussion of this on emacs-devel@gnu.org (i just searched on the archive in vain), because you got me curious. "There are no benchmarks mentioned in the patch has anybody seen this discussed?" Is asking pretty much the same you are asking yet indicating you _have_ read the link, so your response is _not_ low effort but the frustration (which I share). See where I came from?

https://lists.gnu.org/archive/html/emacs-devel/2022-02/msg00858.html Regarding the 2nd part, you're right, my response could have been more informative, asking for information, inviting for a discussion. I could have done better. That's fair. The link dropping just made me upset, that's all.

I'm on mobile currently - the bytecode stack patch is part of the "sorting in C" thread?? Somewhere hidden in there?

Ok I'm not alone not finding things on the emacs devel list... the indexer on the list archive seems to be malfunctioning. Here is a (indirect) link to a mirror with a working indexer: https://lists.gnu.org/archive/html/emacs-devel/2022-03/msg00191.html

I share your frustration... I guess nobody is to blame as such benchmarking is non-existant --- here is the one discussion of the patch I found, which is unrelated to goals or measurement. https://lists.gnu.org/archive/html/emacs-devel/2022-03/msg00330.html on the other hand a lot is going on in terms of bytecode interpreter rewrite and jit and fun and I can only assume to try this and other things is part of a bigger picture that has been discussed in the past, and we are witnesses of the execution of that.

There is no such word 'seperate'.

https://youtu.be/w6P03sTzSqM

well, Emacs does come with a profiler which can probably give some empirical numbers for common tasks to see if this change results in a measurable improvements...

Mattias does great work. Interested to see how this develops and what the consequences will be for garbage collection.