public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juno.krahn at nih dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55345] New: ICE with abstract interface type with use-renamed local names Date: Thu, 15 Nov 2012 18:07:00 -0000 [thread overview] Message-ID: <bug-55345-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55345 Bug #: 55345 Summary: ICE with abstract interface type with use-renamed local names Classification: Unclassified Product: gcc Version: 4.6.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: juno.krahn@nih.gov If an abstract interface type is renamed in the USE statement, and one of those names includes the original name, an ICE can occur. Example code (bug.f90): ---------------------------------- module mod1 abstract interface subroutine func_t() end subroutine func_t end interface end module mod1 module bug use mod1, func_t=>func_t, func1_t=>func_t end module bug ---------------------------------- Result: $ gfortran -c bug2.f90 bug.f90:8:0: internal compiler error: in gfc_trans_use_stmts, at fortran/trans-decl.c:3886 Please submit a full bug report, with preprocessed source if appropriate. See <http://bugzilla.redhat.com/bugzilla> for instructions. If the two USE statements are switched, no ICE occurs. It also succeeds if the rename statements are within an ONLY list.
next reply other threads:[~2012-11-15 18:07 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-15 18:07 juno.krahn at nih dot gov [this message] 2012-11-15 20:04 ` [Bug fortran/55345] " dominiq at lps dot ens.fr 2012-11-16 15:56 ` juno.krahn at nih dot gov 2013-01-10 15:06 ` mikael 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-55345-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: 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).