|Subject:||Re: [ft-devel] fttrigon: Use standard floating-point functions for performance?|
|Date:||Tue, 27 May 2014 10:18:07 -0400|
While profiling libass in OSX's Instruments.app, I've found that Freetype's stroker tends to come up as a very time-consuming routine, and that most of the time spent in the stroker is in the trigonometry routines; specifically, the atan2 and cosine functions seem rather slow.
While it most likely makes sense to leave the current fixed-point trigonometry in place for the sake of systems with slow (or no) FPU, it seems apparent to me that floating-point versions should be used when compiling for modern processors.
|[Prev in Thread]||Current Thread||[Next in Thread]|