A note regarding the subject line of this message:

   "Dead primitive ... Let's get rid of it"

If this means "stop using primitive nnn in the image", then fine. If
it means "remove primitive nnn from the VM", it is not fine at all.
The reason is that VMs need to be able to support older images that
depend on that numbered primitive assignment.

This by the way is that reason that the use of numbered primitives
is a Very Bad Thing. I wish we could come up with a way to stop
doing that. Maybe there could be some way to generate a numbered
primitive table dynamically for the jit without hard coding the
assignments in initializePrimitiveTable in the VM?

Dave


On Thu, Jul 07, 2022 at 02:33:24PM +0200, Marcel Taeumel wrote:
> Hi Tony, hi all --
> 
> Note that the performance of TrueType text composition was improved with Squeak 6.0. We do not try to use primitive 103 in that case anymore.
> 
> Best,
> Marcel
> Am 17.02.2022 12:44:18 schrieb Tony Garnock-Jones <tonyg at leastfixedpoint.com>:
> On 2/17/22 12:33, Marcel Taeumel wrote:
> > Nevermind. The primitive 103 fails for TTCFont (200%) but not for
> > StrikeFont (125%). Yet, the only performance issues I noticed where from
> > a too small GlyphCacheSize.
> 
> Yeah, I'm not seeing a performance difference either now I've reenabled
> it. I guess it's still there, but that code path isn't being stressed
> anymore, so it's not noticeable.
> 
> Cheers,
> Tony

>