public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/38220] C_LOC intrinsic non-pure and without explicit interface Date: Tue, 06 Jan 2009 13:06:00 -0000 [thread overview] Message-ID: <20090106130559.11575.qmail@sourceware.org> (raw) In-Reply-To: <bug-38220-13648@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from tkoenig at gcc dot gnu dot org 2009-01-06 13:05 ------- This appears to resolve the issue(s): Index: interface.c =================================================================== --- interface.c (revision 143076) +++ interface.c (working copy) @@ -2411,9 +2411,12 @@ void gfc_procedure_use (gfc_symbol *sym, gfc_actual_arglist **ap, locus *where) { - /* Warn about calls with an implicit interface. */ + /* Warn about calls with an implicit interface. Special case + for calling a ISO_C_BINDING because these c_loc and c_funloc + are pseudo-unknown. */ if (gfc_option.warn_implicit_interface - && sym->attr.if_source == IFSRC_UNKNOWN) + && sym->attr.if_source == IFSRC_UNKNOWN + && ! sym->attr.is_iso_c) gfc_warning ("Procedure '%s' called with an implicit interface at %L", sym->name, where); Index: symbol.c =================================================================== --- symbol.c (revision 143076) +++ symbol.c (working copy) @@ -4169,6 +4169,7 @@ generate_isocbinding_symbol (const char tmp_sym->result = tmp_sym; tmp_sym->attr.external = 1; tmp_sym->attr.use_assoc = 0; + tmp_sym->attr.pure = 1; tmp_sym->attr.if_source = IFSRC_UNKNOWN; tmp_sym->attr.proc = PROC_UNKNOWN; } -- tkoenig at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |tkoenig at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2009-01-06 13:05:59 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38220
next prev parent reply other threads:[~2009-01-06 13:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-21 22:03 [Bug fortran/38220] New: " dfranke at gcc dot gnu dot org 2008-12-09 20:31 ` [Bug fortran/38220] " dfranke at gcc dot gnu dot org 2008-12-09 20:51 ` dfranke at gcc dot gnu dot org 2009-01-06 13:06 ` tkoenig at gcc dot gnu dot org [this message] 2009-01-06 23:03 ` tkoenig at gcc dot gnu dot org 2009-01-06 23:05 ` tkoenig at gcc dot gnu dot org [not found] <bug-38220-4@http.gcc.gnu.org/bugzilla/> 2014-12-12 7:00 ` Joost.VandeVondele at mat dot ethz.ch 2015-05-16 6:08 ` tkoenig at gcc dot gnu.org 2023-03-15 11:03 ` jeff.science at gmail dot com 2023-03-15 20:45 ` anlauf at gcc dot gnu.org 2023-03-16 20:07 ` anlauf 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=20090106130559.11575.qmail@sourceware.org \ --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).