Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: ezannoni@redhat.com, jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: [rfa/dwarf-1/comments] update dwarf-1 status info
Date: Sat, 24 Apr 2004 06:42:00 -0000	[thread overview]
Message-ID: <20040424064222.4A2914B104@berman.michael-chastain.com> (raw)

This patch updates the dwarfread.c info on the state of dwarf-1.

. gcc 3.4.0 has removed support for dwarf-1 (cheer!)
. i found another user bug report from 2003-07-25 about diab 4.4b.
. diab 5.0.1, released 2002-07-31, supports both dwarf-1 and dwarf-2
. absoft fortran 90/95, released 2001, supports both dwarf-1 and dwarf-2

Testing: this is a comment-only patch.  I built gdb and that's it.

I plan to propose the obsoletion of dwarf-1 soon, but that proposal
is separate from this patch.  This patch just provides current
information, without any opinions or policy judgements.

Okay to commit?

===

2004-04-24  Michael Chastain  <mec.gnu@mindspring.com>

	* dwarfread.c: Update documentation on the state of dwarf-1.

Index: dwarfread.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarfread.c,v
retrieving revision 1.37
diff -c -3 -p -r1.37 dwarfread.c
*** dwarfread.c	14 Feb 2004 15:46:32 -0000	1.37
--- dwarfread.c	24 Apr 2004 06:15:19 -0000
***************
*** 29,35 ****
  
     DWARF-1 is slowly headed for obsoletion.
  
!    In gcc HEAD 2003-11-29 16:28:31 UTC, no targets prefer dwarf-1.
  
     In gcc 3.3.2, these targets prefer dwarf-1:
  
--- 29,35 ----
  
     DWARF-1 is slowly headed for obsoletion.
  
!    In gcc 3.4.0, support for dwarf-1 has been removed.
  
     In gcc 3.3.2, these targets prefer dwarf-1:
  
***************
*** 73,83 ****
     Some non-gcc compilers produce dwarf-1: 
  
       PR gdb/1179 was from a user with Diab C++ 4.3.
       Other users have also reported using Diab compilers with dwarf-1.
       On 2003-06-09 the gdb list received a report from a user
         with Absoft ProFortran f77 which is dwarf-1.
  
!    -- chastain 2003-12-01
  */
  
  /*
--- 73,94 ----
     Some non-gcc compilers produce dwarf-1: 
  
       PR gdb/1179 was from a user with Diab C++ 4.3.
+      On 2003-07-25 the gdb list received a report from a user
+       with Diab Compiler 4.4b.
       Other users have also reported using Diab compilers with dwarf-1.
+ 
+      Diab Compiler Suite 5.0.1 supports dwarf-2/dwarf-3 for C and C++.
+      (Diab(tm) Compiler Suite 5.0.1 Release Notes, DOC-14691-ZD-00,
+      Wind River Systems, 2002-07-31).
+ 
       On 2003-06-09 the gdb list received a report from a user
         with Absoft ProFortran f77 which is dwarf-1.
  
!      Absoft ProFortran Linux Fortran User Guide (no version,
!      but copyright dates are 1991-2001) says that Absoft ProFortran
!      supports -gdwarf1 and -gdwarf2.
! 
!    -- chastain 2004-04-24
  */
  
  /*


             reply	other threads:[~2004-04-24  6:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-24  6:42 Michael Elizabeth Chastain [this message]
2004-04-29 16:09 ` Jim Blandy

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=20040424064222.4A2914B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    /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