public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33686] FORALL loop gives wrong result
Date: Mon, 08 Oct 2007 20:03:00 -0000 [thread overview]
Message-ID: <20071008200255.2569.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33686-7816@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from pault at gcc dot gnu dot org 2007-10-08 20:02 -------
(In reply to comment #6)
Oh dear, oh dear, we are going to have to implement
PROGRAM TST
IMPLICIT NONE
INTEGER :: P(4),I
integer, allocatable :: Q(:)
P = (/2,4,1,3/)
allocate (Q(size(P)))
FORALL(I=1:4)
Q(P(I)) = I
END FORALL
P = Q
deallocate (Q)
PRINT *, P
END PROGRAM TST
when the dependency is detected. In fact, this should not be too bad. It can
be entirely enclosed within trans-stmt.c(generate_loop_for_temp_to_lhs). I have
some hotel room time coming up....
Paul
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33686
next prev parent reply other threads:[~2007-10-08 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 7:17 [Bug fortran/33686] New: " enok at lysator dot liu dot se
2007-10-08 9:13 ` [Bug fortran/33686] " pinskia at gcc dot gnu dot org
2007-10-08 9:42 ` enok at lysator dot liu dot se
2007-10-08 11:28 ` burnus at gcc dot gnu dot org
2007-10-08 12:05 ` dominiq at lps dot ens dot fr
2007-10-08 12:16 ` burnus at gcc dot gnu dot org
2007-10-08 19:03 ` pault at gcc dot gnu dot org
2007-10-08 20:03 ` pault at gcc dot gnu dot org [this message]
2007-10-10 6:50 ` pault at gcc dot gnu dot org
2007-10-10 9:35 ` dominiq at lps dot ens dot fr
2007-10-12 13:26 ` pault at gcc dot gnu dot org
2007-10-12 13:47 ` dominiq at lps dot ens dot fr
2007-10-24 10:00 ` pault at gcc dot gnu dot org
2007-10-29 14:14 ` burnus at gcc dot gnu dot org
2007-10-29 14:15 ` burnus at gcc dot gnu dot 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=20071008200255.2569.qmail@sourceware.org \
--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).