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, fweimer, gregory.p.smith, methane, nascheme, pitrou, skrah, tgrigg, twouters, vstinner
Date 2019-04-16.10:20:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555410056.85.0.30702477069.issue27987@roundup.psfhosted.org>
In-reply-to
Content
> I wonder if we can add -fmax-type-align=8 for extension types...

No, we cannot: it's a temporary fix. The flag causes compilation error if it's added to old version of clang or to a C compiler different than clang.


> Any ideas about reduce impact for Python 3.7?

I don't think that it's a matter of performance here. What matters the most here is correctness.

See Florian Weimer's message:
https://bugs.python.org/issue36618#msg340261

"This issue potentially affects all compilers, not just Clang."
History
Date User Action Args
2019-04-16 10:20:56vstinnersetrecipients: + vstinner, twouters, nascheme, gregory.p.smith, pitrou, benjamin.peterson, methane, skrah, fweimer, tgrigg
2019-04-16 10:20:56vstinnersetmessageid: <1555410056.85.0.30702477069.issue27987@roundup.psfhosted.org>
2019-04-16 10:20:56vstinnerlinkissue27987 messages
2019-04-16 10:20:56vstinnercreate