From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Toon Moene <toon@moene.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
ams@codesourcery.com
Cc: Fortran List <fortran@gcc.gnu.org>
Subject: Re: [PATCH 18/25] Fix interleaving of Fortran stop messages
Date: Wed, 05 Sep 2018 18:11:00 -0000 [thread overview]
Message-ID: <CAO9iq9H7tqsih-v-TeZM=-qisx49BV11odNb1W5z5B-v8kuadA@mail.gmail.com> (raw)
In-Reply-To: <994a9ec6-2494-9a83-cc84-bd8a551142c5@moene.org>
On Wed, Sep 5, 2018 at 7:57 PM Toon Moene <toon@moene.org> wrote:
>
>
>
> -------- Forwarded Message --------
> Subject: [PATCH 18/25] Fix interleaving of Fortran stop messages
> Date: Wed, 5 Sep 2018 12:51:19 +0100
> From: ams@codesourcery.com
> To: gcc-patches@gcc.gnu.org
>
>
> 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-05 Kwok Cheung Yeung <kcy@codesourcery.com>
>
> libgfortran/
> * runtime/minimal.c (estr_write): Define in terms of write.
> ---
> libgfortran/runtime/minimal.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
>
Ok, thanks.
--
Janne Blomqvist
next prev parent reply other threads:[~2018-09-05 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ba94a85fe9c01c57e474a4cc6b7171cc0adb351.1536144068.git.ams@codesourcery.com>
2018-09-05 16:57 ` Fwd: " Toon Moene
2018-09-05 17:15 ` Bernhard Reutner-Fischer
2018-09-05 18:11 ` Janne Blomqvist [this message]
2018-09-12 13:55 ` Andrew Stubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO9iq9H7tqsih-v-TeZM=-qisx49BV11odNb1W5z5B-v8kuadA@mail.gmail.com' \
--to=blomqvist.janne@gmail.com \
--cc=ams@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=toon@moene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).