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 gregory.p.smith
Recipients gregory.p.smith, pablogsal, vstinner
Date 2019-04-12.22:49:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555109360.79.0.509703723042.issue36618@roundup.psfhosted.org>
In-reply-to
Content
Even if you check for -fmax-type-align compiler support at configure time, there is a potential problem:

Nothing guarantees that extension modules are built by the same compiler that CPython is.  If CPython used an old clang without support for that flag and the extension module compiled by that CPython via pip and setup.py, etc. uses a more recent version of clang - it wouldn't specify that flag and the extension module code could be broken.

I suppose this issue of conditional compiler flags is nothing new.  It should not block us from going forward with a workaround like your PRs for now.
History
Date User Action Args
2019-04-12 22:49:20gregory.p.smithsetrecipients: + gregory.p.smith, vstinner, pablogsal
2019-04-12 22:49:20gregory.p.smithsetmessageid: <1555109360.79.0.509703723042.issue36618@roundup.psfhosted.org>
2019-04-12 22:49:20gregory.p.smithlinkissue36618 messages
2019-04-12 22:49:20gregory.p.smithcreate