public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/108663] Accepts invalid bug with pdtXXX
Date: Fri, 03 Feb 2023 21:32:06 +0000	[thread overview]
Message-ID: <bug-108663-4-IHPh28ZYdP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108663-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
> $ gfortran-13-20221218 -c z1.f90   # missing error
> $
> $ gfortran-13-20230115 -c z1.f90
> z1.f90:12:7:
> 
>    12 |    use m, only: t, pdtt, s
>       |       1
> internal compiler error: in check_complete_insertion, at hash-table.h:578

For the record, the entity 'pdtt' is not specified
in the module.  It is constructed by gfortran in 
decl.cc(gfc_get_pdt_instance) when parsing a parameterized
derived type.  The symbol pdtt means PDT type t, and it
appears to inserted into the namespace.  A likely better
name would have been _PDT_t, because the leading underscore
means the name cannot conflict with a user's code and
gfortran downcases all parsed code so PDT shows that the
symbol is artificial.

  reply	other threads:[~2023-02-03 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 20:42 [Bug fortran/108663] New: " jakub at gcc dot gnu.org
2023-02-03 21:32 ` sgk at troutmask dot apl.washington.edu [this message]
2023-06-30  8:54 ` [Bug fortran/108663] " pault 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-108663-4-IHPh28ZYdP@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).