➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients benjamin.peterson, eric.smith, mark.dickinson, serhiy.storchaka, vstinner
Date 2017-04-24.09:03:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493024634.2.0.157511669302.issue30124@psf.upfronthosting.co.za>
In-reply-to
Content 
> Could we use Clang specific pragma in dtoa.c rather than a compiler option?

If we decide to go for the -fno-strict-aliasing only for dtoa.c, I suggest to use it also for GCC. GCC might decide to also optimize dtoa.c further in the future. I don't think that the flag has a major impact on performance if it's restricted to dtoa.c, and it would simplify the build system to only have "per compiler" flags. (Ex: Does ICC also "miscompile" dtoa?)

FreeBSD uses the following syntax to only add the flag on a specific C file. Does it work with GNU and BSD make? (is it a "portable" syntax?)

   CFLAGS.gdtoa_${src}+=-fno-strict-aliasing

See https://svnweb.freebsd.org/changeset/base/313706 (linked from http://bugs.python.org/issue30104#msg292001).
History
Date User Action Args
2017-04-24 09:03:54vstinnersetrecipients: + vstinner, mark.dickinson, eric.smith, benjamin.peterson, serhiy.storchaka
2017-04-24 09:03:54vstinnersetmessageid: <1493024634.2.0.157511669302.issue30124@psf.upfronthosting.co.za>
2017-04-24 09:03:54vstinnerlinkissue30124 messages
2017-04-24 09:03:53vstinnercreate