In article <cahu5pryq3xegtd-7ahzmdbwk32nprfxz24dfdm1oj-wnmyj...@mail.gmail.com>, Cyd Haselton <chasel...@gmail.com> wrote: > Just checking: is sincos() the same as sin() and cos()? Nm output for > my toolchain's libm does show sin() and cos() just not sincos()
See, this is what you get when you ask for free help: bad info. sincos isn't the same, as a little of googling informs me. But, as the thread starting here indicates: https://sourceware.org/ml/binutils/2010-04/msg00219.html gcc can do an optimization that turns a pair of sin() and cos() calls with the same arguments into a single call to sincos(). And there is such a pair in Python's complexobject.c. As the thread explains, there are some platforms where sin() and cos() are implemented but not sincos(). As suggested in the thread, one approach is to give options to gcc to avoid the optimizations: CFLAGS='-fno-builtin-sin -fno-builtin-cos' That does seem to result in a libpython with no references to sincos. -- Ned Deily, n...@acm.org -- https://mail.python.org/mailman/listinfo/python-list