Bug 1749576
Summary: | [Amazon RHEL8.2 FEAT] Python3 - Enable "Expensive" Optimizations | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jon Masters <jcm> |
Component: | python3 | Assignee: | Charalampos Stratakis <cstratak> |
Status: | CLOSED ERRATA | QA Contact: | Lukáš Zachar <lzachar> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.2 | CC: | bgray, cstratak, dshaks, frival, jfeeney, jshortt, kabbott, perfbz, pviktori, torsava, vstinner |
Target Milestone: | rc | Keywords: | FutureFeature, TestCaseNotNeeded |
Target Release: | 8.2 | ||
Hardware: | aarch64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python3-3.6.8-18.el8 | Doc Type: | Release Note |
Doc Text: |
The profile guided optimizations, previously enabled only for the x86_64 architecture, have been also enabled for the aarch64, ppc64le and s390x architectures.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-04-28 16:07:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1732354, 1749568, 1776957 |
Description
Jon Masters
2019-09-05 22:15:51 UTC
# On some architectures, the optimized build takes tens of hours, possibly # longer than Koji's 24-hour timeout. Disable optimizations here. %bcond_with optimizations A solution for that is to backport the following change from Python 3.8 (upstream) to Python 3.6 (downstream): * https://bugs.python.org/issue36044 * https://github.com/python/cpython/commit/4e16a4a3112161a5c6981c0588142d4a4673a934 * https://github.com/python/cpython/commit/e1b900247227dad49d8231f1d028872412230ab4 In short: the PGO build runs only a few tests rather than the full Python test suite to train the compiler, so the build is way faster. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1764 |