public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95829] New: Bogus error with additional blanks in type(*)
Date: Mon, 22 Jun 2020 20:23:09 +0000	[thread overview]
Message-ID: <bug-95829-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95829
           Summary: Bogus error with additional blanks in type(*)
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Affects versions down to at least r5 :


$ cat z1.f90
subroutine s(x)
   type( * ) :: x
end


$ cat z2.f90
subroutine s (a, b, c, d, e, f, g)
   type(*) :: a
   type(* ) :: b
   type( *) :: c
   type( * ) :: d
   type(*  ) :: e
   type(  *) :: f
   type(  *  ) :: g
end


$ gfortran-11-20200621 -c z1.f90
z1.f90:2:4:

    2 |    type( * ) :: x
      |    1
Error: Unclassifiable statement at (1)

             reply	other threads:[~2020-06-22 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 20:23 gscfq@t-online.de [this message]
2020-06-22 23:31 ` [Bug fortran/95829] " kargl at gcc dot gnu.org
2020-07-01  9:14 ` cvs-commit at gcc dot gnu.org
2020-07-01 10:23 ` cvs-commit at gcc dot gnu.org
2020-07-01 12:10 ` cvs-commit at gcc dot gnu.org
2020-07-01 13:08 ` cvs-commit at gcc dot gnu.org
2020-07-01 13:09 ` markeggleston 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-95829-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).