Bug 1726641
| Summary: | Request a backport of fixes for SVE Vector PCS on AArch64 (gcc part) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Nick Clifton <nickc> |
| Component: | gcc | Assignee: | Marek Polacek <mpolacek> |
| gcc sub component: | gcc-toolset-9 | QA Contact: | Alexandra Petlanová Hájková <ahajkova> |
| Status: | CLOSED ERRATA | Docs Contact: | Kevin Owen <kowen> |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | ahajkova, fweimer, jakub, law, mcermak, mnewsome, mpolacek, ohudlick, otikhomi |
| Version: | --- | Keywords: | Bugfix |
| Target Milestone: | rc | ||
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gcc-toolset-9-gcc-9.2.1-2.1.el8 | Doc Type: | Bug Fix |
| Doc Text: |
.Advanced SIMD functions on the 64-bit ARM architecture no longer miscompile when lazily resolved
Previously, the new vector Procedure Call Standard (PCS) for Advanced SIMD did not properly save and restore certain callee-saved registers when lazily resolving Advanced SIMD functions. As a consequence, binaries could misbehave at runtime. With this update, the Advanced SIMD and SVE vector functions in the symbol table are marked with `.variant_pcs` and, as a result, the dynamic linker will bind such functions early.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-04-28 15:58:37 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: | 1724130, 1755139 | ||
|
Description
Nick Clifton
2019-07-03 10:56:56 UTC
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/RHBA-2020:1683 |