public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51946] file compiles properly on IBM xlf compiler and cary compiler
Date: Sun, 22 Jan 2012 19:22:00 -0000 [thread overview]
Message-ID: <bug-51946-4-w364rGhLbv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51946-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51946
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2012-01-22 18:16:38 UTC ---
On Sun, Jan 22, 2012 at 05:45:27PM +0000, burnus at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51946
>
> --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-22 17:45:27 UTC ---
> (In reply to comment #0)
> > Created attachment 26412
> > taken from Damian Rouson's book , allocate seems to be the culprit
> > Source if from Damian Rouson from Sandia National Laboratories
> > It compiles properly with IBM xlf and Cray fortran compilers.
> > apparently the allocate statement
> > Allocate ( localprdct, source = rhs)
> > is the culprit
>
> I have to admit that I could not find that allocate statement. Neither in your
> attachment nor in the book's resources available at
> http://www.cambridge.org/rouson under "Resources available".
>
My guess is that it is line 204:
allocate(local_product,source=rhs)
next prev parent reply other threads:[~2012-01-22 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 17:03 [Bug fortran/51946] New: " dominique.pelletier at polymtl dot ca
2012-01-22 17:14 ` [Bug fortran/51946] " kargl at gcc dot gnu.org
2012-01-22 17:17 ` burnus at gcc dot gnu.org
2012-01-22 17:31 ` burnus at gcc dot gnu.org
2012-01-22 18:17 ` burnus at gcc dot gnu.org
2012-01-22 19:22 ` sgk at troutmask dot apl.washington.edu [this message]
2012-01-22 19:55 ` [Bug fortran/51946] file compiles properly on IBM xlf compiler and Cray compiler dominique.pelletier at polymtl dot ca
2012-01-22 20:15 ` dominique.pelletier at polymtl dot ca
2012-01-22 20:26 ` kargl at gcc dot gnu.org
2012-01-22 22:25 ` burnus at gcc dot gnu.org
2012-01-23 17:57 ` burnus at gcc dot gnu.org
2012-01-27 10:10 ` pault at gcc dot gnu.org
2012-01-27 10:38 ` 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-51946-4-w364rGhLbv@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).