From: Mikael Morin <mikael.morin@sfr.fr>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>,
"Steve Kargl" <sgk@troutmask.apl.washington.edu>
Cc: paul Thomas <paul.richard.thomas@gmail.com>,
gfortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR fortran/67805 -- Check for invalid charlength
Date: Sat, 24 Oct 2015 20:44:00 -0000 [thread overview]
Message-ID: <562BED92.9090306@sfr.fr> (raw)
In-Reply-To: <A4317D62-B912-40F3-A306-5C97D62B95C6@lps.ens.fr>
Le 24/10/2015 21:29, Dominique d'Humières a écrit :
> At revision r229288 compiling the following test
>
[...]
>
> while it compiles without error at r229261.
>
I believe the accesses to ref->u.ar should be guarded with ref->type ==
REF_ARRAY.
Steve, a patch doing that is preapproved.
Mikael
next prev parent reply other threads:[~2015-10-24 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 19:29 Dominique d'Humières
2015-10-24 20:44 ` Mikael Morin [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-23 19:28 Steve Kargl
2015-10-23 19:29 ` Steve Kargl
2015-10-24 5:51 ` Paul Richard Thomas
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=562BED92.9090306@sfr.fr \
--to=mikael.morin@sfr.fr \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=sgk@troutmask.apl.washington.edu \
/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).