From: Christophe Lyon <christophe.lyon@linaro.org>
To: Jerry DeLisle <jvdelisle@charter.net>
Cc: Janne Blomqvist <blomqvist.janne@gmail.com>,
gfortran <fortran@gcc.gnu.org>,
gcc patches <gcc-patches@gcc.gnu.org>
Subject: Re: [6 Regession] Usage of unitialized pointer io/list_read.c (
Date: Wed, 17 Feb 2016 08:36:00 -0000 [thread overview]
Message-ID: <CAKdteOYd=KrOSKLPORBc9WahMKPhX6g-qmqfmCifehM-2THfkg@mail.gmail.com> (raw)
In-Reply-To: <56C36132.2050805@charter.net>
On 16 February 2016 at 18:49, Jerry DeLisle <jvdelisle@charter.net> wrote:
> On 02/16/2016 12:06 AM, Christophe Lyon wrote:
>> On 15 February 2016 at 23:16, Janne Blomqvist <blomqvist.janne@gmail.com> wrote:
>>> On Mon, Feb 15, 2016 at 11:45 PM, Jerry DeLisle <jvdelisle@charter.net> wrote:
>>>> The title of the PR should be "Mishandling of namelist comments" or
>>>> "Interpreting '!' as a comment in non-namelist reads".
> --- snip ---
>>
>> Although OK in trunk, I've noticed regressions in the gcc-5 branch
>> since you commtted
>> r233442:
>>
>
> There is a subsequent commit that updates those two failing cases,
> namelist_38.f90 and namelist_84.f90.
>
> Please check that you have those updates and let me know if they still fail.
>
Indeed, the subsequent commit fixed them, thanks.
> Regards,
>
> Jerry
>
next prev parent reply other threads:[~2016-02-17 8:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 21:45 Jerry DeLisle
2016-02-15 22:16 ` Janne Blomqvist
2016-02-16 0:07 ` Jerry DeLisle
2016-02-16 8:06 ` Christophe Lyon
2016-02-16 17:49 ` Jerry DeLisle
2016-02-17 8:36 ` Christophe Lyon [this message]
2016-02-16 13:17 Dominique d'Humières
2016-02-16 17:59 ` Jerry DeLisle
2016-02-16 19:38 ` Dominique d'Humières
2016-02-16 20:50 ` Jerry DeLisle
2016-02-17 1:37 ` Jerry DeLisle
2016-02-17 17:02 ` Jerry DeLisle
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='CAKdteOYd=KrOSKLPORBc9WahMKPhX6g-qmqfmCifehM-2THfkg@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=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).