[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> 2010-11-26 21:32:39 UTC ---

Notes:  

(temporary work-arounds)

1. for Fortran, one can effect a fix by altering the dsymutil spec in
config/darwin.h and config/darwin9.h thus:

.c|.cc|.C|.cpp|.cp|.c++|.cxx|.CPP|.m|.mm|.s|.f|.f90|.f95|.f03|.f77|.for|.F|.F90|.F95|.F03:

2. The generic 'failing' is that the spec is looking at only the last item on
the c/l -- if that happens to be a source file, the dSYM will be generated.  
There isn't a generic facility to recognize *any* source file and post a flag
(perhaps something worth considering in 4.7).

So, you need to make at least one of your source files the last entry on the
c/l.

3. To avoid the need for the dSYM at all -- if all you want to do is to debug
locally -- just use "-save-temps".

4. Note that there are incompatibilities between the current debug output of
FSF gcc and dsymutil  - we cannot 'fix' dsymutil as it is closed source.  At
present, these cause irritating but harmless warnings.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> 2010-11-27 09:29:24 UTC ---
(In reply to comment #5)

Firstly, the patch mentioned at comment #2 is withdrawn - it's no longer
functional.

> 1. for Fortran, one can effect a fix by altering the dsymutil spec in
> config/darwin.h and config/darwin9.h thus:
> 
> .c|.cc|.C|.cpp|.cp|.c++|.cxx|.CPP|.m|.mm|.s|.f|.f90|.f95|.f03|.f77|.for|.F|.F90|.F95|.F03:
> 
> 2. The generic 'failing' is that the spec is looking at only the last item on
> the c/l -- if that happens to be a source file, the dSYM will be generated.  
> There isn't a generic facility to recognize *any* source file and post a flag
> (perhaps something worth considering in 4.7).
> 
> So, you need to make at least one of your source files the last entry on the
> c/l

Well this used to work, but no longer does.
The recent change to append the libgfortran.spec to the c/l means that one can
no longer do this.

we need a purpose-made capability to flag (any) source file present on the
command line [any language].

> 3. To avoid the need for the dSYM at all -- if all you want to do is to debug
> locally -- just use "-save-temps".

this is the only current work-around for exes built from source in a single
c/l.

(NOTE: when the objects are built and linked in separate stages, the dSYM is
not required in any event - since the objects are present in the build dir and
not deleted until the user does so.)

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> 2010-12-02 11:49:41 UTC ---
proposed  work-around for 4.6

http://gcc.gnu.org/ml/gcc-patches/2010-12/msg00145.html

Note the following web-page describes the intended usage/behavior of dsymutil

http://wiki.dwarfstd.org/index.php?title=Apple's_%22Lazy%22_DWARF_Scheme

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[mrs at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

mrs@gcc.gnu.org <mrs at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mrs at gcc dot gnu.org

--- Comment #8 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2010-12-02 22:27:34 UTC ---
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.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains at gcc dot gnu.org]

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.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[mikestump at comcast dot net]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #10 from Mike Stump <mikestump at comcast dot net> 2010-12-03 20:17:03 UTC ---
Jack says that some of the spurious warnings are fixed in Xcode 3.2.3.  I have
3.2.4 on my system.  Could you update Xcode and see if any we care about
remain.  If so, please file a Apple bug report.  If fixed, we can simply
require the newer Xcode.  If it won't work on darwin9, and we care, we could
have the .f addition in darwin10.h alone.  I don't favor the stripping, but I'g
go along with a darwin9 stripper and a darwin10 and later no strip version.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.6.0                       |---

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[howarth at nitro dot med.uc.edu]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

Jack Howarth <howarth at nitro dot med.uc.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |howarth at nitro dot
                   |                            |med.uc.edu

--- Comment #11 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-12-03 23:01:13 UTC ---
(In reply to comment #10)
> Jack says that some of the spurious warnings are fixed in Xcode 3.2.3.  I have
> 3.2.4 on my system.  Could you update Xcode and see if any we care about
> remain.  If so, please file a Apple bug report.  If fixed, we can simply
> require the newer Xcode.  If it won't work on darwin9, and we care, we could
> have the .f addition in darwin10.h alone.  I don't favor the stripping, but I'g
> go along with a darwin9 stripper and a darwin10 and later no strip version.

FYI, this was radar 7851516.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[howarth at nitro dot med.uc.edu]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #12 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-12-04 22:00:39 UTC ---
The problem dsymutil issues are fixed for darwin10 when using Xcode 3.2.4 and
the patch...

Index: gcc/config/darwin10.h
===================================================================
--- gcc/config/darwin10.h    (revision 167446)
+++ gcc/config/darwin10.h    (working copy)
@@ -28,3 +28,12 @@

 #undef TARGET_ASM_EMIT_UNWIND_LABEL
 #define TARGET_ASM_EMIT_UNWIND_LABEL default_emit_unwind_label
+
+/* Since DWARF2 is default, conditions for running dsymutil are different.  */
+/* Xcode 3.2.3 and later have radar 7851516 fixed. */
+#undef DSYMUTIL_SPEC
+#define DSYMUTIL_SPEC \
+   "%{!fdump=*:%{!fsyntax-only:%{!c:%{!M:%{!MM:%{!E:%{!S:\
+   
%{.c|.cc|.C|.cpp|.cp|.c++|.cxx|.CPP|.m|.mm|.s|.f|.f90|.f95|.f03|.f77|.for|.F|.F90|.F95|.F03:
\
+    %{g*:%{!gstabs*:%{!g0: " DSYMUTIL " %{o*:%*}%{!o:a.out}}}}}}}}}}}}"
+

http://gcc.gnu.org/ml/gcc-testresults/2010-12/msg00289.html

Using the same approach in gcc/config/darwin9.h reveals that Xcode 3.1.4 still
produces three types of warnings from dsymutil. These are of the form...

warning: DWARFDebugInfoEntry::AppendDependants() -- check on this item
TAG_subrange_type: attr =  AT_upper_bound  form = FORM_ref4^M
warning: DWARFDebugInfoEntry::AppendDependants() -- check on this item
TAG_subrange_type: attr =  AT_upper_bound  form = FORM_ref4
arning: {0x0000026d} TAG_variable:  AT_location( 0x00000000 ) didn't have valid
function low pc, the location list will be incorrect.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[howarth at nitro dot med.uc.edu]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #13 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-12-04 22:02:00 UTC ---
The second form of the error should have been...

warning: DWARFDebugInfoEntry::AppendDependants() -- check on this item
TAG_subrange_type: attr =  AT_lower_bound  form = FORM_ref4

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[howarth at nitro dot med.uc.edu]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #14 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-12-05 19:58:17 UTC ---
Created attachment 22646
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22646
patch to expand source types that call dsymutil for darwin9 and later

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[howarth at nitro dot med.uc.edu]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #15 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-12-05 20:01:27 UTC ---
The testresults on x86_64-apple-darwin9 for the proposed patch expanding the
source files types calling dsymutil and the pruning the warnings from dsymutil
due to bugs in Xcode 3.1.x are posted at...

http://gcc.gnu.org/ml/gcc-testresults/2010-12/msg00380.html

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[howarth at nitro dot med.uc.edu]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #16 from Jack Howarth <howarth at nitro dot med.uc.edu> 2010-12-05 20:12:30 UTC ---
As a refresher, the original comments from the Apple dsymutil maintainer on the
FORM_ref4 were...

------------------------------------------------
The warning was cause for alarm, and the root cause has been fixed 
(checked in), though it isn't affecting your test case.

If you see this type of warning again before you get a fixed dsymutil, 
look at the dwarfdump output as you were doing for a matching attribute 

value. In this case it was:

0x00000205:         TAG_subrange_type [28] =20
                     AT_type[FORM_ref4] ( {0x00000048} ( base  ) )
                     AT_upper_bound[FORM_ref4] ( {0x00000149} )

Then you want to make sure that the reference (FORM_ref4) it has 
({0x00000149}) made it into the output file which it did:

0x00000149:         TAG_variable [21] =20
                     AT_artificial[FORM_flag] ( 0x01 )
                     AT_type[FORM_ref4] ( {0x0000020f} ( const base  ) )
                     AT_location[FORM_data4] ( 0x00000144
                        0x0000000100000d46 - 0x0000000100000e62: r13-1
                        0x0000000100000e64 - 0x0000000100000e6f: r13-1 )


So everything is ok in this case.

dsymutil will track exactly which DIEs make it into the dSYM and only 
put those DIEs and the dependent DIEs. This helps deal with gcc's one 
definition rule which can bloat up the debug info. If dead code 
stripping is on, and only one function of 100 makes it into the dSYM, we 
strip 99% of the debug info and keep the DWARF small. In a failing case, 
dsymutil would not add 0x00000149 to the output dSYM and the DWARF would 
have a DIE with an invalid reference.
------------------------------------------------
So pruning these errors will mask the fact that darwin9 may potentially
generate bad DWARF debug information. Alternatively we could drop the pruning
and move the expansion of the source types to gcc/config/darwin10.h per Comment
12 if we always want to have pristine DWARF generated.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #17 from Iain Sandoe <iains at gcc dot gnu.org> 2010-12-05 20:26:53 UTC ---
dsymutil will generate the same issues for languages already enabled (there are
some cases in the c/c++ test-suite on i686-Darwin9).

my 0.02 euros:
  I  would prefer to have it enabled for Darwin9 - since that is the last
usable case for ppc (if the test-suite prune approach works, then I much prefer
that over a hack script).

  If dsymutil is buggy on Darwin9, there is nothing we can currently do - since
I don't imagine that there will be another update for XCode on Darwin9.  Not
enabling it is simply hiding a problem - not solving it.

(maybe one day we'll have time to roll our own and then the dependency will be
resolved).

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #18 from Iain Sandoe <iains at gcc dot gnu.org> 2010-12-10 11:01:10 UTC ---
Author: iains
Date: Fri Dec 10 10:40:43 2010
New Revision: 167683

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167683
Log:

dsymutil enabled for Fortran.

2010-12-10  Jack Howarth  <howarth@bromo.med.uc.edu>
        Iain Sandoe  <iains@gcc.gnu.org>

    PR 43751/target

gcc:
    * config/darwin9.h (DSYMUTIL_SPEC): Add fortran source types.

testsuite:

    * lib/prune.exp: Prune dsymutil warnings.

libstadc++-v3:

    * testsuite/lib/prune.exp: Prune dsymutil warnings.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/darwin9.h
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/lib/prune.exp
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/testsuite/lib/prune.exp

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[mrs at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

mrs@gcc.gnu.org <mrs at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

--- Comment #19 from mrs at gcc dot gnu.org <mrs at gcc dot gnu.org> 2010-12-10 17:17:00 UTC ---
Fixed.  Thanks.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[dominiq at lps dot ens.fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |burnus at gcc dot gnu.org,
                   |                            |iains at gcc dot gnu.org
         Resolution|FIXED                       |---

--- Comment #20 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This PR has reappeared after r205679 with warnings of the kind

warning: DWARFDebugInfoEntry::AppendDependants() -- check on this item
TAG_namelist_item: attr =  AT_namelist_item  form = FORM_ref4

They are silenced with the following change of the regexp added at r167683:

--- gcc/testsuite/lib/prune.exp    2013-04-26 10:21:37.000000000 +0200
+++ ../work/gcc/testsuite/lib/prune.exp    2013-12-11 16:42:00.000000000 +0100
@@ -59,7 +59,7 @@ proc prune_gcc_output { text } {

     # Ignore harmless warnings from Xcode 3.2.x.
     regsub -all "(^|\n)\[^\n\]*ld: warning: can't add line info to anonymous
symbol\[^\n\]*" $text "" text
-    regsub -all "(^|\n)\[^\n\]*warning:
DWARFDebugInfoEntry::AppendDependants\[^\n\]*AT_\[^\n\]*_bound\[^\n\]*FORM_ref4\[^\n\]*"
$text "" text
+    regsub -all "(^|\n)\[^\n\]*warning:
DWARFDebugInfoEntry::AppendDependants\[^\n\]*AT_\[^\n\]*FORM_ref4\[^\n\]*"
$text "" text
     regsub -all "(^|\n)\[^\n\]*warning:\[^\n\]*TAG_variable: 
AT_location\[^\n\]*didn't have valid function low pc\[^\n\]*" $text "" text

     # Ignore harmless warnings from Xcode 4.0.

I hope this change will survive any fix for pr59438!

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[dominiq at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #21 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Wed Apr  2 08:34:45 2014
New Revision: 209016

URL: http://gcc.gnu.org/viewcvs?rev=209016&root=gcc&view=rev
Log:
2014-04-02  Dominique d'Humieres  <dominiq@lps.ens.fr>

    PR target/43751
    * lib/prune.exp: Modify the regular express to prune
    the new warnings introduced by r205679 on darwin9.


Modified:
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/lib/prune.exp

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[dominiq at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

--- Comment #22 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Fri Apr  4 06:43:56 2014
New Revision: 209070

URL: http://gcc.gnu.org/viewcvs?rev=209070&root=gcc&view=rev
Log:
2014-03-26  Dominique d'Humieres  <dominiq@lps.ens.fr>

    PR target/43751
    * lib/prune.exp: Modify the regular express to prune
    the new warnings introduced by r205679 on darwin9.


Modified:
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog
    branches/gcc-4_8-branch/gcc/testsuite/gfortran.dg/fmt_en.f90

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[dominiq at lps dot ens.fr]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #23 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Wrong entry.

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains at gcc dot gnu dot org]

------- Comment #4 from iains at gcc dot gnu dot org  2010-04-14 17:37 -------
see: 
http://gcc.gnu.org/ml/gcc-patches/2010-04/msg00806.html
for a proposed resolution to this.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains 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

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[steven at gcc dot gnu dot org]

------- Comment #2 from steven at gcc dot gnu dot org  2010-04-14 09:24 -------
Does FSF gcc-4.2 exhibit the problem? Maybe the OSX compiler has local changes
in the specs processing.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751

[Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.

[iains at gcc dot gnu dot org]

------- Comment #1 from iains at gcc dot gnu dot org  2010-04-14 09:06 -------
I'll take this for now - since I've got a patch in progress that ought to fix
it.


-- 

iains at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |iains at gcc dot gnu dot org
                   |dot org                     |
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-04-14 09:06:32
               date|                            |
   Target Milestone|---                         |4.6.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751