public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64933] ASSOCIATE on a character variable does not allow substring expressions
Date: Fri, 13 Feb 2015 15:36:00 -0000 [thread overview]
Message-ID: <bug-64933-4-5V18wosWpl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64933-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64933
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #3 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #2)
> Up to revision r219797 (2015-01-17), I get the error
>
> pr64933.f90:5:31:
>
> ASSOCIATE(should_work=>char_var)
> 1
> Error: Associate-name 'should_work' at (1) is used as array
>
> Starting at r219823 (2015-01-18) I get the ICE. Likely a fall out of r219814
> (pr55901). Please feel free to mark this PR as a 5.0 regression.
Hmm! I am not sure that it can be regarded as a regression, since the original
error was wrong. I agree that an ICE is worse.... -ish.
I'll take it though, regression or not.
Paul
prev parent reply other threads:[~2015-02-13 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 10:22 [Bug fortran/64933] New: " olivier.marsden at ecmwf dot int
2015-02-04 10:24 ` [Bug fortran/64933] " olivier.marsden at ecmwf dot int
2015-02-13 13:56 ` dominiq at lps dot ens.fr
2015-02-13 15:36 ` pault at gcc dot gnu.org [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=bug-64933-4-5V18wosWpl@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).