You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2017-10-06.04:15:16.903>created_at=<Date2017-10-04.20:56:25.072>labels= ['easy', 'build', '3.7']
title="don't mention GCC in sys.version when built with Clang"updated_at=<Date2017-10-06.04:15:16.902>user='https://github.com/benjaminp'
When built with clang, Python reports that it was built with something like "GCC 4.2.1 Compatible Clang 4.0.0 (tags/RELEASE_400/rc1)". This is because clang pretends to be GCC 4.2.1 for the purposes of the __VERSION__ preprocessor macro. We should use __clang_version__ when clang is being used.
(Possibly we should simply use the first line of "$CC --version" as the compiler version of record rather than writing preprocessor tests in getcompiler.c.)
New changeset 7faf7e5 by Benjamin Peterson in branch 'master':
closes bpo-31696: don't mention GCC in sys.version when building with clang (bpo-3891) 7faf7e5
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: