public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at pci dot uzh.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25071] dummy argument larger than actual argument
Date: Thu, 27 Jan 2011 13:42:00 -0000	[thread overview]
Message-ID: <bug-25071-4-d1tVap6aV4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-25071-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Joost VandeVondele <Joost.VandeVondele at pci dot uzh.ch> 2011-01-27 13:22:49 UTC ---
I actually vaguely recall why this should be a warning, and not be checked for
at runtime. This is for legacy codes using real :: a(1) instead of real ::
a(*). Something like

SUBROUTINE S1(a)
  INTEGER :: a(10)
  a(10)=0
END SUBROUTINE

SUBROUTINE S2(a)
  INTEGER :: a(1)
  CALL S1(a)
END SUBROUTINE

INTEGER :: a(10)
CALL S2(a)
END

'works just fine'...


  parent reply	other threads:[~2011-01-27 13:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-25071-4@http.gcc.gnu.org/bugzilla/>
2011-01-25 12:41 ` jb at gcc dot gnu.org
2011-01-25 12:47 ` Joost.VandeVondele at pci dot uzh.ch
2011-01-25 12:51 ` burnus at gcc dot gnu.org
2011-01-27 11:02 ` burnus at gcc dot gnu.org
2011-01-27 13:42 ` Joost.VandeVondele at pci dot uzh.ch [this message]
2015-09-06  1:08 ` dominiq at lps dot ens.fr
2005-11-26 17:55 [Bug fortran/25071] New: better diagnostic needed jv244 at cam dot ac dot uk
2005-11-26 19:48 ` [Bug fortran/25071] dummy argument larger than actual argument fxcoudert at gcc dot gnu dot org
2007-04-19 15:16 ` burnus at gcc dot gnu dot org
2007-05-03 19:50 ` patchapp at dberlin dot org
2007-05-04  7:54 ` burnus at gcc dot gnu dot org
2007-05-04  7:55 ` burnus at gcc dot gnu dot org
2007-07-24  9:42 ` 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=bug-25071-4-d1tVap6aV4@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).