Because the hardware environment has changed, and the tradeoffs on integer and floating-point arithmetic are different. (Like it says in the Wikipedia article.) Out of order execution might be messing up your measurements, too.
---------- message ---------- From: "uǝlƃ ↙↙↙" <[email protected]> To: FriAM <[email protected]> Cc: Bcc: Date: Thu, 7 Jan 2021 15:24:15 -0800 Subject: [FRIAM] Q_rsqrt() vs 1/sqrt() https://en.wikipedia.org/wiki/Fast_inverse_square_root So, why is Q_rsqrt() *slower* than 1/sqrt()? 1/sqrt() took 0.294771 s Q_rsqrt() took 0.51579 s -- ↙↙↙ uǝlƃ
- .... . -..-. . -. -.. -..-. .. ... -..-. .... . .-. . FRIAM Applied Complexity Group listserv Zoom Fridays 9:30a-12p Mtn GMT-6 bit.ly/virtualfriam un/subscribe http://redfish.com/mailman/listinfo/friam_redfish.com archives: http://friam.471366.n2.nabble.com/ FRIAM-COMIC http://friam-comic.blogspot.com/
