3 ms·

https://www.atwillys.de/content/cc/sine-lookup-for-embedded-in-c/?lang=en https://www.atwillys.de/content/cc/sine-lookup-for-embedded-... Have you checked out

https://www.atwillys.de/content/cc/sine-lookup-for-embedded-in-c/?lang=en https://www.atwillys.de/content/cc/sine-lookup-for-embedded-... Have you checked out this? Its an alternative implementation which uses interpolated table lookup and requires only 66 bytes of constant memory with an error of less than 0.05% compared to the floating point sine.

lifthrasiir 4y ago
The (presumably relative) error of 0.05% implies only ~11 significant bits, while 32-bit and 64-bit floating point formats have 24 and 53 significant bits respectively. If your sine has only 11 correct bits and you are okay with that, why do you have much more than 11 bits of input precision after all? EDIT: Someone (sorry, the comment was removed before I could cite one) mentioned that it is actually for Q1.15 fixed point. So it was not even an "alternative" implementation...
- deleted 4y ago
  [deleted]