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/108451] [13 Regression] ICE in check_complete_insertion, at hash-table.h:578 Date: Wed, 18 Jan 2023 18:25:24 +0000 [thread overview] Message-ID: <bug-108451-4-HaWJEKO8aB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108451-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108451 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |accepts-invalid, | |ice-on-invalid-code --- Comment #1 from G. Steinmetz <gscfq@t-online.de> --- Following variant z2 should be rejected similar to z3 : $ cat z2.f90 module m type t(n) integer, len :: n integer :: a(n) end type contains subroutine s(x) type(t(2)) :: x end end program p use m, only: t, s, pdtt type(t(2)) :: y call s(y) end $ cat z3.f90 module m type t end type contains subroutine s end end program p use m, only: t, s, pdtt call s end $ gfortran-13-20230115 -c z2.f90 # missing error $ $ gfortran-13-20230115 -c z3.f90 z3.f90:9:21: 9 | use m, only: t, s, pdtt | 1 Error: Symbol 'pdtt' referenced at (1) not found in module 'm'
next prev parent reply other threads:[~2023-01-18 18:25 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-18 18:24 [Bug fortran/108451] New: " gscfq@t-online.de 2023-01-18 18:25 ` gscfq@t-online.de [this message] 2023-01-19 7:47 ` [Bug fortran/108451] " rguenth at gcc dot gnu.org 2023-01-19 14:22 ` marxin at gcc dot gnu.org 2023-02-03 13:50 ` jakub at gcc dot gnu.org 2023-02-03 17:07 ` kargl at gcc dot gnu.org 2023-02-03 20:38 ` cvs-commit at gcc dot gnu.org 2023-02-03 20:41 ` jakub at gcc dot gnu.org 2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:21 ` cvs-commit 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-108451-4-HaWJEKO8aB@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: linkBe 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).