public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/50537] explicit interface required (r178939) Date: Mon, 04 May 2015 10:02:00 -0000 [thread overview] Message-ID: <bug-50537-4-iFJhb1FDSf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50537-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50537 --- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- Since gcc version 4.9.2 and up to trunk (6.0) I now get pr50537_db.f90:5:24: character(len=2) f 1 Error: Explicit interface required for 'f' at (1): result with non-constant character length Does it mean that this PR is now fixed?
next prev parent reply other threads:[~2015-05-04 10:02 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-27 14:18 [Bug fortran/50537] New: " zeccav at gmail dot com 2013-02-26 19:58 ` [Bug fortran/50537] " dominiq at lps dot ens.fr 2013-02-27 14:01 ` burnus at gcc dot gnu.org 2015-05-04 9:49 ` tkoenig at gcc dot gnu.org 2015-05-04 10:02 ` dominiq at lps dot ens.fr [this message] 2015-08-31 16:41 ` zeccav at gmail dot com
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-50537-4-iFJhb1FDSf@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).