Bug 1731555

Summary: Add notes wrt gcc Fortran async IO
Product: Red Hat Developer Toolset Reporter: Marek Polacek <mpolacek>
Component: doc-Release_NotesAssignee: Lenka Špačková <lkuprova>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: DTS 9.0 RHEL 7CC: jhradile, lkuprova, mcermak, mnewsome, tborcin, vslavik
Target Milestone: alpha   
Target Release: 9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Executable files created with Red Hat Developer Toolset are dynamically linked in a nonstandard way. As a consequence, Fortran code cannot handle input/output (I/O) operations asynchronously even if this functionality is requested. To work around this problem, link the `libgfortran` library statically with the `-static-libgfortran` option to enable asynchronous I/O operations in Fortran code. Note that Red Hat discourages static linking for security reasons.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-16 13:33:20 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:

Description Marek Polacek 2019-07-19 18:25:01 UTC
We should mention this in Release Notes:

While upstream GCC 9 supports Fortran async IO really asynchronously, when linking dynamically with DTS 9 it will be synchronous (with -static-libgfortran asynchronous), because there is nothing we can do about that in our system library + nonshared blob way of linking - the async changes are all through the library.