Bug 1711346 - Backport workaround for broken C/C++ wrappers to LAPACK
Summary: Backport workaround for broken C/C++ wrappers to LAPACK
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gcc
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Marek Polacek
QA Contact: Alexandra Petlanová Hájková
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-17 14:42 UTC by Marek Polacek
Modified: 2023-07-18 14:19 UTC (History)
8 users (show)

Fixed In Version: gcc-8.3.1-4.4.el8
Doc Type: Bug Fix
Doc Text:
Previously, invalid C/C++ wrappers calling Fortran subroutines with single-character string arguments that failed to include the hidden string length argument could cause a crash at run-time. The crash could occur because when tail call optimization takes place, the caller's arguments are overwritten, which could have lead to stack corruption if the string length argument hadn't been provided. GCC offers a workaround for this problem; the -ftail-call-workaround option is now available, which disables tail call optimization for Fortran subroutines with character arguments. Red Hat recommends that users fix the C/C++ wrappers instead of using this workaround option.
Clone Of:
Environment:
Last Closed: 2019-11-05 22:16:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNU Compiler Collection 90329 0 None None None 2019-08-05 20:55:36 UTC
Red Hat Product Errata RHBA-2019:3565 0 None None None 2019-11-05 22:16:46 UTC

Description Marek Polacek 2019-05-17 14:42:26 UTC
This came recently in BZ 1709538.  Jakub submitted a patch implementing a workaround for such wrong code upstream:
https://gcc.gnu.org/ml/gcc-patches/2019-05/msg00915.html

We should probably include this patch in out RHEL 8 system compiler.

Comment 8 errata-xmlrpc 2019-11-05 22:16:40 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-2019:3565


Note You need to log in before you can comment on or make changes to this bug.