From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30605 invoked by alias); 3 Dec 2010 08:58:39 -0000 Received: (qmail 30596 invoked by uid 22791); 3 Dec 2010 08:58:38 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 03 Dec 2010 08:58:34 +0000 From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs. X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: iains at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: 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 Date: Fri, 03 Dec 2010 08:58:00 -0000 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: 2010-12/txt/msg00251.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751 --- Comment #9 from Iain Sandoe 2010-12-03 08:58:25 UTC --- (In reply to comment #8) > Please add a comment with a testcase that fails to work. I tried the obvious > one, and when .f is added to darwin9.h, it worked. Indeed, between my comment #6 and yours the (suffix) problem has been resolved (5 days can be a long time in gcc, it seems ;) ). (probably fixed by r167292) so placing: ".c|.cc|.C|.cpp|.cp|.c++|.cxx|.CPP|.m|.mm|.s|.f|.f90|.f95|.f03|.f77|.for|.F|.F90|.F95|.F03:" in config/darwin{,9}.h is now functional - I've tried a variety of representative command lines without fail - so it looks like the underlying issue has been resolved. Of course, residual issues [spurious warnings] with dsymutil are outside our control (other than wrapping the utility in some way). However, other than resolving this, we could enable for Fortran. To resolve the spurious warnings, we will either (a) Have to wrap dsymutil in some script to suppress the spurious messages .. (I made a script referenced in comment #4) .. or (b) Go through the test-suite and put in "prune" lines in the cases that will now fail on "excess errors". -- (a) is somewhat hacky - but does have the advantage that it is a fix in one place rather than distributing stuff around the test-suite.