public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53576] New: Very unhelpful error message: "Unclassifiable statement" instead of "Can't convert TYPE to ..." Date: Mon, 04 Jun 2012 17:52:00 -0000 [thread overview] Message-ID: <bug-53576-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53576 Bug #: 53576 Summary: Very unhelpful error message: "Unclassifiable statement" instead of "Can't convert TYPE to ..." Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org The following program is invalid; gfortran rejects it, but with a completely unhelpful error message. The problem is that the "amn(jj)" should be "amn%value(jj). Current error message: wfn & 1 Error: Unclassifiable statement at (1) Expected error (or something similar): = amn(jj) 1 Error: Can't convert TYPE(amn_t) to COMPLEX(4) at (1) Note: gfortran prints the proper error message if the loop bound is changed from "amn%nsites" to, e.g., "5". (That's how I got the type-conversion error message.) program simple_wf_op_gen type :: amn_t integer :: nsites = 0 complex :: value(1) end type amn_t type(amn_t) :: amn integer :: jj complex :: wfn do jj = 1, amn%nsites wfn & = amn(jj) end do end program simple_wf_op_gen
next reply other threads:[~2012-06-04 17:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-04 17:52 burnus at gcc dot gnu.org [this message] 2015-10-08 8:59 ` [Bug fortran/53576] " dominiq at lps dot ens.fr
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-53576-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).