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 skrah
Recipients David.Edelsohn, cstratak, fweimer, mark.dickinson, skrah, vstinner
Date 2019-01-17.15:44:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1547739897.03.0.552305299161.issue35752@roundup.psfhosted.org>
In-reply-to
Content
> For me, the main risk is to forget to remove the workaround once a new GCC version will be released (in N months).

This is why I suggested using the reproducer in configure.ac, setting something
like HAVE_GCC_MEMCPY_ROUNDING_BUG and then either a) wrap the *entire* PACK_SINGLE()
macro in an #ifdef or b) *preferably* add a global flag like -fno-inline or any
other flag that prevents the issue to CFLAGS.

b) under the condition that any such flag exists.


I may do a) in the weekend, which also addresses Florian Weimer's observation
that it is not known whether the issue is limited to POWER.
History
Date User Action Args
2019-01-17 15:44:58skrahsetrecipients: + skrah, mark.dickinson, vstinner, fweimer, David.Edelsohn, cstratak
2019-01-17 15:44:57skrahsetmessageid: <1547739897.03.0.552305299161.issue35752@roundup.psfhosted.org>
2019-01-17 15:44:57skrahlinkissue35752 messages
2019-01-17 15:44:56skrahcreate