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/25071] dummy argument larger than actual argument Date: Thu, 19 Apr 2007 15:16:00 -0000 [thread overview] Message-ID: <20070419151643.7867.qmail@sourceware.org> (raw) In-Reply-To: <bug-25071-6642@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from burnus at gcc dot gnu dot org 2007-04-19 16:16 ------- Analogously for character lengths: program test character(len=10) :: x call foo(x) write(*,*) 'X=',x contains subroutine foo(y) character(len=20) :: y y = 'hello world' end subroutine end Taken from: http://ftp.aset.psu.edu/pub/ger/fortran/test/ test17.f90 (slightly modified). g95: Actual character argument at (1) is shorter in length than the formal argument NAG f95: Character length too short for arg Y (no. 1) of FOO ifort: Character length argument mismatch. [X] -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25071
next prev parent reply other threads:[~2007-04-19 15:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 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 [this message] 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 [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 2015-09-06 1:08 ` 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=20070419151643.7867.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: linkBe 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).