public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bdavis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41160]  New: No more than one complex function in a file
Date: Tue, 25 Aug 2009 00:20:00 -0000	[thread overview]
Message-ID: <bug-41160-8277@http.gcc.gnu.org/bugzilla/> (raw)

gfortran gives an error, g77 accepts it without a problem



[bdavis@localhost ~/tmp]$ cat a.f
      COMPLEX FUNCTION F0_HDEC*16(M1,M2,QSQ)
      RETURN
      END
      COMPLEX FUNCTION F1_HDEC*16(M1,M2,QSQ)
      RETURN 
      END
[bdavis@localhost ~/tmp]$ /home/bdavis/g77/run/bin/g77 -c a.f
[bdavis@localhost ~/tmp]$ gfortran -c a.f
a.f:1.30:

      COMPLEX FUNCTION F0_HDEC*16(M1,M2,QSQ)                            
                              1
Error: Expected formal argument list in function definition at (1)
a.f:4.30:

      COMPLEX FUNCTION F1_HDEC*16(M1,M2,QSQ)                            
                              1
Error: Expected formal argument list in function definition at (1)
a.f:2.72:

      RETURN                                                            
                                                                        1
a.f:5.72:

      RETURN                                                            
                                                                        2
Error: Two main PROGRAMs at (1) and (2)


-- 
           Summary: No more than one complex function in a file
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: bdavis at gcc dot gnu dot org


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


             reply	other threads:[~2009-08-25  0:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25  0:20 bdavis at gcc dot gnu dot org [this message]
2009-08-25  0:36 ` [Bug fortran/41160] " kargl at gcc dot gnu dot org
2009-08-25  0:40 ` kargl at gcc dot gnu dot org
2009-08-25  2:04 ` bdavis at gcc dot gnu dot org
2009-08-25  2:10 ` jvdelisle at gcc dot gnu dot org
2009-08-25  2:29 ` kargl 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-41160-8277@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).