| commit | 4cd947bb413958ca2c9ee1e203d0d7fcf38e517d | |
| author | ams <ams@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Wed, 12 Sep 2018 13:53:34 +0000 (12 13:53 +0000) | ||
| committer | ams <ams@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Wed, 12 Sep 2018 13:53:34 +0000 (12 13:53 +0000) | ||
| tree | 854875f5b91ae1001d9e908f3f2447010a0ce667 | treesnapshot (tar.gz zip) |
| parent | c55843761ee68181da8999336b941cb7894b94bc | commitdiff |
Fix interleaving of Fortran STOP messages
Fortran STOP and ERROR STOP use a different function to print the "STOP" string
and the message string. On GCN this results in out-of-order output, such as
"<msg>ERROR STOP ".
This patch fixes the problem by making estr_write use the proper Fortran write,
not C printf, so both parts are now output the same way. This also ensures
that both parts are output to STDERR (not that that means anything on GCN).
2018-09-12 Kwok Cheung Yeung <kcy@codesourcery.com>
libgfortran/
* runtime/minimal.c (estr_write): Define in terms of write.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@264239 138bc75d-0d04-0410-961f-82ee72b054a4
Fortran STOP and ERROR STOP use a different function to print the "STOP" string
and the message string. On GCN this results in out-of-order output, such as
"<msg>ERROR STOP ".
This patch fixes the problem by making estr_write use the proper Fortran write,
not C printf, so both parts are now output the same way. This also ensures
that both parts are output to STDERR (not that that means anything on GCN).
2018-09-12 Kwok Cheung Yeung <kcy@codesourcery.com>
libgfortran/
* runtime/minimal.c (estr_write): Define in terms of write.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@264239 138bc75d-0d04-0410-961f-82ee72b054a4
| libgfortran/ChangeLog | diffblobblamehistory | |
| libgfortran/runtime/minimal.c | diffblobblamehistory |