➜

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, dim, eric.smith, mark.dickinson, serhiy.storchaka, vstinner
Date 2017-05-02.14:11:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493734273.31.0.60700103255.issue30124@psf.upfronthosting.co.za>
In-reply-to
Content 
dtoa.c is now compiled with -fno-string-aliasing (for any clang version, not only clang 4.0) on Python 3.5, 3.6 and 3.7.

It was decided to not touch dtoa.c to not diverge from upstream.

Thanks Dimitry Andric and Mark Dickinson for your reviews and support in this cryptic issue!

Note 1: We consider that Clang 4.0 is wrong, whereas GCC respects the C99 standard for aliasing on unions. But I don't think that it matters much who is wrong or not :-)

Note 2: Python 2.7 already used -fno-strict-aliasing on all .c files because of its design of PyObject structures, fixed in Python 3.
History
Date User Action Args
2017-05-02 14:11:13vstinnersetrecipients: + vstinner, mark.dickinson, eric.smith, benjamin.peterson, serhiy.storchaka, dim
2017-05-02 14:11:13vstinnersetmessageid: <1493734273.31.0.60700103255.issue30124@psf.upfronthosting.co.za>
2017-05-02 14:11:13vstinnerlinkissue30124 messages
2017-05-02 14:11:13vstinnercreate