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/47054] Compilation error when cray pointers are declared in both host and internal subroutines
Date: Thu, 23 Dec 2010 19:33:00 -0000 [thread overview]
Message-ID: <bug-47054-4-rVTRUQl537@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47054-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47054
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2010-12-23 19:33:04 UTC ---
> What compilation error?
For me it is
[macbook] f90/bug% gfc -fcray-pointer pr47054.f90
pr47054.f90:23.29:
pointer (paxg_8, G_xg_8(G_ni))
1
Error: Symbol 'g_xg_8' at (1) has no IMPLICIT type
pr47054.f90:24.29:
pointer (payg_8, G_yg_8(G_nj))
1
Error: Symbol 'g_yg_8' at (1) has no IMPLICIT type
next prev parent reply other threads:[~2010-12-23 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 18:04 [Bug fortran/47054] New: " deji_aking at yahoo dot ca
2010-12-23 19:23 ` [Bug fortran/47054] " kargl at gcc dot gnu.org
2010-12-23 19:33 ` dominiq at lps dot ens.fr [this message]
2011-01-03 15:51 ` deji_aking at yahoo dot ca
2011-01-03 22:39 ` kargl at gcc dot gnu.org
2011-01-03 22:42 ` kargl at gcc dot gnu.org
2011-01-03 23:59 ` kargl at gcc dot gnu.org
2014-05-13 14:22 ` dominiq at lps dot ens.fr
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-47054-4-rVTRUQl537@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).