public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.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.
Date: Fri, 03 Dec 2010 08:58:00 -0000 [thread overview]
Message-ID: <bug-43751-4-cVVh53O0nd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43751-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751
--- Comment #9 from Iain Sandoe <iains at gcc dot gnu.org> 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.
next prev parent reply other threads:[~2010-12-03 8:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43751-4@http.gcc.gnu.org/bugzilla/>
2010-11-26 22:08 ` iains at gcc dot gnu.org
2010-11-27 9:55 ` iains at gcc dot gnu.org
2010-12-02 11:49 ` iains at gcc dot gnu.org
2010-12-02 22:27 ` mrs at gcc dot gnu.org
2010-12-03 8:58 ` iains at gcc dot gnu.org [this message]
2010-12-03 20:17 ` mikestump at comcast dot net
2010-12-03 22:32 ` rguenth at gcc dot gnu.org
2010-12-03 23:01 ` howarth at nitro dot med.uc.edu
2010-12-04 22:01 ` howarth at nitro dot med.uc.edu
2010-12-04 22:02 ` howarth at nitro dot med.uc.edu
2010-12-05 19:58 ` howarth at nitro dot med.uc.edu
2010-12-05 20:01 ` howarth at nitro dot med.uc.edu
2010-12-05 20:12 ` howarth at nitro dot med.uc.edu
2010-12-05 20:27 ` iains at gcc dot gnu.org
2010-12-10 12:41 ` iains at gcc dot gnu.org
2010-12-10 17:17 ` mrs at gcc dot gnu.org
2013-12-13 15:18 ` dominiq at lps dot ens.fr
2014-04-02 8:35 ` dominiq at gcc dot gnu.org
2014-04-04 6:44 ` dominiq at gcc dot gnu.org
2014-04-04 6:49 ` dominiq at lps dot ens.fr
2010-04-14 9:00 [Bug target/43751] New: " iains at gcc dot gnu dot org
2010-04-14 9:07 ` [Bug target/43751] " iains at gcc dot gnu dot org
2010-04-14 9:24 ` steven at gcc dot gnu dot org
2010-04-14 9:50 ` iains at gcc dot gnu dot org
2010-04-14 17:38 ` iains at gcc dot gnu dot 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=bug-43751-4-cVVh53O0nd@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: link
Be 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).