This brings a new compiler which seems to have fewer bugs than the old one, and may also generate slightly more efficient code. There is also a new menu for SPI speed which can largely be ignored.
Please note that Arduno 2.x is required to install this. It can still be used with Arduino 1.x, but only after you install it with Arduno 2.x (or manually).
How about “Periphereal Clock:” half or full ?
Ah, yes, that’s the SPI clock.
Leave it at half unless you have a large SPI display.
Done.
So far seems to be working on my preferred Arduino 1.8.19. 
I just flashed 1 new font/blade style with the 4.1 and more than half of my font/blade styles looks really weird , some wrong colors and other errors i could only show it in a video …
Do they start working again if you go back to 3.6?
If you want to post a video, you’ll need to upload it somewhere else, like youtube, google photos or facebook and the link it here.
I re flashed it with 3.6 and now its back to normal .
I believe that the blade styles that did have spark tip and power-flash where the ones working with errors
And you didn’t change anything else?
What version of ProffieOS are you using?
Can you post your config file?
I did not change anything else , same settings . OS7.14 arduino 2.3.3
I flashed again with 4.1 and got the same errors with the blade styles
So I’ve done some experimenting, and there is definitely a difference i how
TrWipeSparkTipX behaves between 3.6 and 4.1. I’m not sure why yet, but hopefully I can figure it out tomorrow, because it’s bedtime.
ok no worries, thank you so much for your time
This is really starting to look like a compiler bug.
Inserting some printouts to debug the problem suddenly made the problem go away…
I’m probably going to have to withdraw 4.1 and see if there is a slightly less buggy version of gcc out there somewhere…
Oh ok, I see, I was checking and there are other effects that also get errors
And notice with 3.6 my memory it’s 67%
And with 4.1 78%
It’s unfortunate, because the compiler also fixed some problems.
I’m going to set up a new gcc (13.3) for the beta version of the arduino-proffieboard plugin, let’s hope it has fewer problems…
Ja, what I did like it’s that it was way faster when loading the config to the board.
I’ll be glad to test, I’m a complete noob but I love doing this 
On a mac?
(Newer arm-gcc comes with support for arm-macs, older ones has to be run through the x86-64 emulation layer…)
Windows 11
Interesting, not sure why that would be faster.
I tried upgrading to gcc 13-3rel1, but the bug seems to still be there unfortunately. 
… and of course the bug only happens when you specify “smallest size” as your optimization level.