Intel BOT seems to be patches for specific binaries (hence why they didn't see a difference for Geekbench 6.7), unlike BOLT/Propeller which are for arbitrary programs. The second image from their help page [1] showcases this.
reply[1] https://www.intel.com/content/www/us/en/support/articles/000...
Applying targeted binary patches shouldn't take 40 seconds... unless that's also a fake "so it looks like it's working really hard" delay.
replyI might be thinking of a different project then...
replyI swore Intel had their own PLO tool, but I can only find https://github.com/clearlinux/distribution/issues/2996.
Found it. It was https://www.phoronix.com/news/Intel-Thin-Layout-Optimizer.
replyIt was open source, but has since been deprecated.
Question: do those vectorize code as in the example here?
I was of the understanding they performed a more limited subset of optimizations.
replyPropeller can’t really do many instruction level modifications due to how it works (constructs a layout file that then gets passed to the linker).
replyBOLT could do this, but does not as far as I’m aware.
Most of vectorization like this is also probably better done in a compiler middle end. At least in LLVM, the loop vectorizer and especially the SLP Vectorizer do a decent job of picking up most of the gains.
You might be able to pick up some gains by doing it post-link at the MC level, but writing an IR level SLP Vectorizer is already quite difficult.