public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.sagan at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49025] New: gfortran bug: Local variable does not hide generic procedure.
Date: Tue, 17 May 2011 15:53:00 -0000	[thread overview]
Message-ID: <bug-49025-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: gfortran bug: Local variable does not hide generic
                    procedure.
           Product: gcc
           Version: 4.5.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: david.sagan@gmail.com


Consider the following test code:

-----------------------------------

module test

interface kick
  subroutine a_kick
  end subroutine
end interface

contains

subroutine my_sub
  implicit none
  integer kick
  call some_sub(kick)
end subroutine

end module

----------------------------------
Compiling gives:

lnx4103:~/dcs/bmad_distribution/test_build> gfortran --version
GNU Fortran (GCC) 4.5.1
Copyright (C) 2010 Free Software Foundation, Inc.

lnx4103:~/dcs/bmad_distribution/test_build> gfortran -c test.f90
test.f90:13.16:

  call some_sub(kick)
                1
Error: GENERIC procedure 'kick' is not allowed as an actual argument at (1)


The local "kick" variable is not hiding the "kick" generic procedure. 
This code compiles with ifort v9 and v12.


             reply	other threads:[~2011-05-17 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 15:53 david.sagan at gmail dot com [this message]
2011-05-17 16:38 ` [Bug fortran/49025] " burnus at gcc dot gnu.org
2011-07-23 23:39 ` pinskia at gcc dot gnu.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-49025-4@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).