public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49636] [F03] ASSOCIATE construct confused with slightly complicated case
Date: Tue, 11 Feb 2014 23:40:00 -0000 [thread overview]
Message-ID: <bug-49636-4-YY1fCjWHMf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49636
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Created attachment 32098 [details]
> A fix for this problem
AFAICT it fixes the problem for 64 bit mode only. In 32 bit mode the ICE is
gone, but I get at run time
i_good= 1 3 5
i_bad= 1********** 3
> I am sure that this trick will fix pr57019 too. This latter is claimed
> to be a regression but I am sure that it never worked :-) Nonetheless,
> I will take advantage of the regression label!
>
> I will work on it tomorrow night.
>
> By the way, this patch regtests OK on trunk. I have to make sure
> that substrings of character arrays work OK with ASSOCIATE.
Did you regtest with -m32? I see gfortran.dg/associated_target_5.f03 failing at
execution time with -m32, as well as the first test in pr57522
0 1 2 3
0 4 1 5
next prev parent reply other threads:[~2014-02-11 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 22:59 [Bug fortran/49636] New: Associate " fkrogh#gcc at mathalacarte dot com
2011-07-04 23:21 ` [Bug fortran/49636] " fkrogh#gcc at mathalacarte dot com
2011-07-05 9:06 ` burnus at gcc dot gnu.org
2014-02-10 9:33 ` [Bug fortran/49636] [F03] ASSOCIATE " dominiq at lps dot ens.fr
2014-02-10 22:14 ` pault at gcc dot gnu.org
2014-02-11 23:40 ` dominiq at lps dot ens.fr [this message]
2014-02-12 9:20 ` paul.richard.thomas at gmail dot com
2015-09-08 9:29 ` dominiq at lps dot ens.fr
2015-10-18 9:21 ` pault at gcc dot gnu.org
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-49636-4-YY1fCjWHMf@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).