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/38487] Bogus Warning: INTENT(INOUT) actual argument might interfere with actual argument
Date: Thu, 11 Dec 2008 16:08:00 -0000	[thread overview]
Message-ID: <20081211160737.13942.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38487-6318@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from burnus at gcc dot gnu dot org  2008-12-11 16:07 -------
Mikael added this as part of PR 35681 with check in
http://gcc.gnu.org/viewcvs?view=rev&revision=141931

See:
http://gcc.gnu.org/viewcvs/trunk/gcc/fortran/dependency.c?r1=141931&r2=141930&pathrev=141931

I think the warning is OK in the sense that the pointer could point to the same
memory address which could potentially make trouble, but still the warning
feels too strong. However, I have not studied neither the test case not
dependency.c in details.

Mikael, what do you think?


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikael at gcc dot gnu dot
                   |                            |org


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


  reply	other threads:[~2008-12-11 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 15:39 [Bug fortran/38487] New: " anlauf at gmx dot de
2008-12-11 16:08 ` burnus at gcc dot gnu dot org [this message]
2008-12-11 22:27 ` [Bug fortran/38487] " anlauf at gmx dot de
2008-12-13 14:30 ` mikael at gcc dot gnu dot org
2008-12-15 18:11 ` mikael at gcc dot gnu dot org
2008-12-21 16:05 ` mikael at gcc dot gnu dot org
2008-12-21 16:21 ` mikael at gcc dot gnu dot org
2009-01-04 19:12 ` mikael at gcc dot gnu dot org
2009-01-14 20:53 ` mikael 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=20081211160737.13942.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).