From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6234 invoked by alias); 29 Jan 2013 12:43:28 -0000 Received: (qmail 6127 invoked by uid 48); 29 Jan 2013 12:43:14 -0000 From: "mikael at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: mikael at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Resolution Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg02650.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44830 Mikael Morin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #2 from Mikael Morin 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 ***