public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/44830] Function return-type declaration with specification expression rejected for renamed derived types Date: Tue, 29 Jan 2013 12:43:00 -0000 [thread overview] Message-ID: <bug-44830-4-9QjDpbEzbf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44830-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44830 Mikael Morin <mikael at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #2 from Mikael Morin <mikael at gcc dot gnu.org> 2013-01-29 12:43:13 UTC --- (In reply to comment #0) > This may be related to bug41370, which is about a similar issue for character > length expressions in the return type. Well, no. It is an issue with USE-renamed symbols and IMPORT. So not related to PR41370. (In reply to comment #1) > The code compiles without error after revision 195506. > If the code is valid as I think, this PR can be closed as fixed with pr53537. > If it is not valid, somebody will have to explain why. Yeah, it's the same problem. The test cases are almost the same. Closing as duplicate. *** This bug has been marked as a duplicate of bug 53537 ***
prev parent reply other threads:[~2013-01-29 12:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44830-4@http.gcc.gnu.org/bugzilla/> 2013-01-28 20:08 ` dominiq at lps dot ens.fr 2013-01-29 12:43 ` mikael at gcc dot gnu.org [this message]
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-44830-4-9QjDpbEzbf@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).