News for hackers. Stuff that matters.
Re:Writing a game engine in pure C: The Graphic Initialization by mikepurvis on Wednesday June 05, 2019 @02:46PM (#20107841)
It seems clang-7 agrees with you— it compiles the multiplication down to shl+add, so the perf is completely identical, see:

http://quick-bench.com/CdxqB_qPD3VS5H7igB31FFoqLLo

Re:Writing a game engine in pure C: The Graphic Initialization by rzzzt on Wednesday June 05, 2019 @03:12PM (#20108073)
But you are also right that it is not a huge difference :) In no-optimization mode, it keeps the imul in for Multiply. the result is 1.2477 vs. 1.2668, relative to Noop.

The site is really cool, thanks for pointing me to it!

Re:Writing a game engine in pure C: The Graphic Initialization by mikepurvis on Wednesday June 05, 2019 @03:47PM (#20108396)
Interestingly, gcc-8 does some really weird stuff. Its version of Multiply is 1.4 times slower than its version of Shift, but according to the disassembly, the Shift implementation is actually using an imul, whereas the Multiply implementation is doing a lea/shl.