public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <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: Mon, 03 Jan 2011 23:59:00 -0000	[thread overview]
Message-ID: <bug-47054-4-E0YC2vZVsx@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 #5 from kargl at gcc dot gnu.org 2011-01-03 23:58:41 UTC ---
The problem appears to be in decl.c(variable_decl)

  /*  If this symbol has already shown up in a Cray Pointer declaration,
      then we want to set the type & bail out.  */
  if (gfc_option.flag_cray_pointer)
    {
      gfc_find_symbol (name, gfc_current_ns, 1, &sym);
      if (sym != NULL && sym->attr.cray_pointee)
    {
      sym->ts.type = current_ts.type;
      sym->ts.kind = current_ts.kind;

When gfc_find_symbol() returns, sym == NULL, so the
if block is skipped.  current_ts.type is BT_REAL and
for the reduced testcase current_ts.kind = 4, which 
is want we want.  I think we may want to have a

if (sym == NULL &&  sym->attr.cray_pointee)
   insert_name_into_current_namespace.

Unfortnately, I can't remember how to do that
and have no time to investigate further.


  parent reply	other threads:[~2011-01-03 23:59 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
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 [this message]
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-E0YC2vZVsx@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).