From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: jerry DeLisle <jvdelisle@charter.net>
Cc: Fortran List <fortran@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Use vectored writes when reporting errors and warnings.
Date: Fri, 21 Sep 2018 18:16:00 -0000 [thread overview]
Message-ID: <CAO9iq9Fuh7+2wq4wkw4JgLDvvG_9nAiKVLUAexkZ4sNAPF2iZQ@mail.gmail.com> (raw)
In-Reply-To: <89a4724d-746e-5ca6-f3b2-f94dcf167ca0@charter.net>
On Fri, Sep 21, 2018 at 7:37 PM Jerry DeLisle <jvdelisle@charter.net> wrote:
> Janne, this looks OK.
Thanks, committed as r264487.
Since you are touching on configuration and posix
> dependencies have you tested under any other systems?
>
No, unfortunately I don't have easy access to such a system for testing.
The patch, as can be seen, contains backwards compatibility stuff for
targets that don't have writev() and struct iovec, but that code is
untested. I'll keep an eye out for regression reports, of course!
--
Janne Blomqvist
prev parent reply other threads:[~2018-09-21 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 19:17 Janne Blomqvist
2018-09-21 8:41 ` Janne Blomqvist
2018-09-21 16:37 ` Jerry DeLisle
2018-09-21 18:16 ` Janne Blomqvist [this message]
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=CAO9iq9Fuh7+2wq4wkw4JgLDvvG_9nAiKVLUAexkZ4sNAPF2iZQ@mail.gmail.com \
--to=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle@charter.net \
/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).