public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40737] Pointer references sometimes fail to define "span" symbols
Date: Wed, 22 Jul 2009 09:21:00 -0000	[thread overview]
Message-ID: <20090722092003.20397.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40737-17946@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from burnus at gcc dot gnu dot org  2009-07-22 09:20 -------
My current understanding is that "span" is only created (in
gfc_get_symbol_decl)
  if (sym->attr.subref_array_pointer)
is true - and is then assumed to live at the same place as the symbol (array
descriptor) itself. But this fails for use association (and maybe also for host
association).

Solution 1: Always create that variable if they symbols is a pointer to an
array.
Solution 2: Defer it until we have the proper array descriptor, which handles
this.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40737


  parent reply	other threads:[~2009-07-22  9:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 21:37 [Bug fortran/40737] New: " dh458 at oakapple dot net
2009-07-13 21:39 ` [Bug fortran/40737] " dh458 at oakapple dot net
2009-07-13 21:40 ` dh458 at oakapple dot net
2009-07-14  7:50 ` burnus at gcc dot gnu dot org
2009-07-21 15:19 ` dh458 at oakapple dot net
2009-07-22  7:11 ` burnus at gcc dot gnu dot org
2009-07-22  7:13 ` burnus at gcc dot gnu dot org
2009-07-22  9:21 ` burnus at gcc dot gnu dot org [this message]
2009-10-06 22:04 ` bergner at gcc dot gnu dot org
2009-10-06 23:10 ` kargl at gcc dot gnu dot org
2009-10-07  8:20 ` burnus at gcc dot gnu dot org
2009-10-07 22:42 ` dh458 at oakapple dot net
     [not found] <bug-40737-4@http.gcc.gnu.org/bugzilla/>
2010-12-28 22:31 ` dfranke at gcc dot gnu.org
2011-01-22 23:46 ` dominiq at lps dot ens.fr
2011-06-23  7:37 ` kenneth.hoste at elis dot ugent.be
2013-01-06 14:56 ` burnus at gcc dot gnu.org
2015-08-30 10:26 ` 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=20090722092003.20397.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).