public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul dot richard dot thomas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45019] Aliasing of TARGET dummy argument not detected correctly
Date: Thu, 22 Jul 2010 10:01:00 -0000	[thread overview]
Message-ID: <20100722100051.31948.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45019-16338@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from paul dot richard dot thomas at gmail dot com  2010-07-22 10:00 -------
Subject: Re:  Aliasing of TARGET dummy argument not 
        detected correctly

Dear Tobias,


> I think the patch below looks fine, however, if I set a break point, the
> function "gfc_check_dependency" is never called for test program. Thus, there
> must be at least another spot where a change is required. Paul, do you have an
> idea where?

Ahhhh.... yes.  Dependencies in assignment go their own sweet way.


trans-array.c:gfc_conv_resolve_dependencies calls gfc_could_be_alias,
which in its turn calls symbol.c:gfc_symbols_could_alias

This latter is where you need to intervene.

Cheers

Paul


-- 


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


  parent reply	other threads:[~2010-07-22 10:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 15:41 [Bug fortran/45019] New: " domob at gcc dot gnu dot org
2010-07-21 15:57 ` [Bug fortran/45019] " burnus at gcc dot gnu dot org
2010-07-21 16:32 ` burnus at gcc dot gnu dot org
2010-07-21 16:44 ` burnus at gcc dot gnu dot org
2010-07-21 16:58 ` burnus at gcc dot gnu dot org
2010-07-21 18:43 ` burnus at gcc dot gnu dot org
2010-07-21 21:37 ` burnus at gcc dot gnu dot org
2010-07-22  6:45 ` burnus at gcc dot gnu dot org
2010-07-22  8:40 ` burnus at gcc dot gnu dot org
2010-07-22 10:01 ` paul dot richard dot thomas at gmail dot com [this message]
2010-07-22 11:35 ` burnus at gcc dot gnu dot org
2010-07-23  8:40 ` burnus at gcc dot gnu dot org
2010-07-23  9:53 ` burnus at gcc dot gnu dot org
2010-09-04 19:21 ` burnus at gcc dot gnu dot org
2010-09-04 19:21 ` 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=20100722100051.31948.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).