public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerhard.steinmetz.fortran@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66495] New: [5 Regression] Issue with same name for embedded function
Date: Wed, 10 Jun 2015 16:30:00 -0000	[thread overview]
Message-ID: <bug-66495-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66495

            Bug ID: 66495
           Summary: [5 Regression] Issue with same name for embedded
                    function
           Product: gcc
           Version: 5.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gerhard.steinmetz.fortran@t-online.de
  Target Milestone: ---

Another test case :
   integer function f()
   contains
      integer function f()
      end
   end

yields (gfortran 5.1.1) :
f951: internal compiler error: Segmentation fault

---

But prints a regular error message with gfortran 4.9.0, 4.8.3 :

$ gfortran -c -g -O0 -Wall -fcheck=all -fno-frontend-optimize s.f90
s.f90:3.21:

   integer function f(y)
                     1
s.f90:1.18:

integer function f(x)
                  2
Error: Procedure 'f' at (1) has an explicit interface and must not have
attributes declared at (2)
s.f90:3.24:

   integer function f(y)
                        1
Error: Symbol 'f' at (1) already has basic type of INTEGER


             reply	other threads:[~2015-06-10 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 16:30 gerhard.steinmetz.fortran@t-online.de [this message]
2015-06-10 19:45 ` [Bug fortran/66495] " dominiq at lps dot ens.fr
2015-06-11  8:14 ` rguenth at gcc dot gnu.org
2015-07-16  9:12 ` rguenth at gcc dot gnu.org
2015-10-02 22:08 ` kargl at gcc dot gnu.org
2015-10-10  8:41 ` 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=bug-66495-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).