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/50933] New: Wrongly regards BIND(C) types as incompatible Date: Mon, 31 Oct 2011 14:20:00 -0000 [thread overview] Message-ID: <bug-50933-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50933 Bug #: 50933 Summary: Wrongly regards BIND(C) types as incompatible Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org gfortran fails to compile the program below. I think the program is valid as the derived type uses BIND(C). Works if one uses SEQUENCE instead of BIND(C) Taken from http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/887251d8cd64eb02 (Richard Maine's example). For some reason, only the part of the issues raised in the thread were fixed in PR 45211; cf. also PR 37829. gfortran compilation fails with: write (*,*) liter_cb(link_info) 1 Error: Type mismatch in argument 'link_info' at (1); passed TYPE(info_t) to TYPE(info_t) MODULE liter_cb_mod USE ISO_C_BINDING CONTAINS FUNCTION liter_cb(link_info) bind(C) USE ISO_C_BINDING IMPLICIT NONE INTEGER(c_int) liter_cb TYPE, bind(C) :: info_t INTEGER(c_int) :: type END TYPE info_t TYPE(info_t) :: link_info liter_cb = 0 END FUNCTION liter_cb END MODULE liter_cb_mod PROGRAM main USE ISO_C_BINDING interface FUNCTION liter_cb(link_info) bind(C) USE ISO_C_BINDING IMPLICIT NONE INTEGER(c_int) liter_cb TYPE, bind(C) :: info_t INTEGER(c_int) :: type END TYPE info_t TYPE(info_t) :: link_info END FUNCTION liter_cb end interface TYPE, bind(C) :: info_t INTEGER(c_int) :: type END TYPE info_t type(info_t) :: link_info write (*,*) liter_cb(link_info) END PROGRAM main
next reply other threads:[~2011-10-31 14:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-31 14:20 burnus at gcc dot gnu.org [this message] 2011-11-02 8:30 ` [Bug fortran/50933] " burnus at gcc dot gnu.org 2011-11-03 22:36 ` burnus at gcc dot gnu.org 2011-11-03 22:44 ` burnus 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-50933-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).