bulk88

https://lemire.me/blog/2012/05/31/data-alignment-for-speed-myth-or-reality/

between ``` SHA-1: 7e2ed756ebc5b1c55afe3e6ba5be424db74ef6e4 * Try to force inlining of newSV_type (i -> I in embed.fnc) ``` and blead's ``` SHA-1: 1b6aef6d141ef8e718ff72add8ed8653f2c7847f * Update Extutils-MakerMaker to CPAN version 7.74 ```...

``` --- pb4164vc22rlb4/t.txt 2025-04-10 20:21:00.483738900 -0400 +++ pb4164vc22rlaf/t.txt 2025-04-10 20:17:25.172423800 -0400 @@ -4,7 +4,7 @@ Directory of C:\pb4164vc22rlaf\bin perl541.dll - 1 File(s) 3,210,240 bytes + 1 File(s) 3,226,624 bytes Directory...

> > At some point in the past couple of dev cycles, this inlining seems to have stopped happening. Possibly additions just tipped it over a size threshold within the...

> > > When `Perl_newSV_type` became an inline function, the idea was that using it to create a specific type known at compile time should result in the call being...

> Thanks for the feedback, all. > > It's good to know that inlining is still happening with clang-21. (I really think the performance improvement is worth it.) The original...

> * Hardcode the relevant values into `newSV_type` - but on DEBUGGING builds there is an assert statement that each of the hardcoded values matches what's actually in the relevant...

> I had thought about per-type functions originally. Can't remember if someone dissuaded me or I just figured that so many new functions would be unwelcome. > > If that's...

> I had thought about per-type functions originally. Can't remember if someone dissuaded me or I just figured that so many new functions would be unwelcome. statics can't be found...

> > Most of the SV types are obsolete Perl 4 holdovers, like FORM and IO objects > > IO is very much in active use: > > $ perl...