This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.
- From: "iains at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Apr 2010 09:49:54 -0000
- Subject: [Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.
- References: <bug-43751-19002@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from iains at gcc dot gnu dot org 2010-04-14 09:49 -------
(In reply to comment #2)
> Does FSF gcc-4.2 exhibit the problem? Maybe the OSX compiler has local changes
> in the specs processing.
OK, it's not a regression - it never worked ;)
FSF 4.2 does not have the dsymutil spec.
FSF 4.3 does, but it fails in the same way as current trunk.
I'll manually compare apple-local-gcc-42/gcc/gcc.c with trunk/gcc/gcc.c as soon
as I have a spare moment.
As far as Fortran is concerned - this is missing from all versions of the spec
(so that needs fixing). The problem at the moment is that adding .f*|.F*
doesn't work (whether I expand the * manually or not).
In my current fix, I'm intending to remove that part of the spec - since, IMO,
it's non-obvious to create a debug sym file for "gcc foo.c -o foo -g " and not
for " gcc foo.o -o foo -g " (despite the reasoning behind that - which is
clear to compiler cognoscenti but not necessarily compiler users).
Of course, that alteration in behavior might not be acceptable to the Darwin
maintainers..
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751