Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Dan Nicolaescu <dann@godzilla.ICS.UCI.EDU>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: gdb-patches@sources.redhat.com, Jason Merrill <jason@redhat.com>
Subject: Re: dwarf2 cleanup
Date: Fri, 16 Feb 2001 14:45:00 -0000	[thread overview]
Message-ID: <200102161444.aa08963@gremlin-relay.ics.uci.edu> (raw)
In-Reply-To: <npbss2d0hb.fsf@zwingli.cygnus.com>

Jim Blandy <jimb@zwingli.cygnus.com> writes:

  > Hi --- this patch looks good.  Do you have a copyright assignment on
  > file with the FSF for GDB?

Unfortunately I don't have one for GDB, only for GCC.  
But I can send one in asap. 

--dan

  > Dan Nicolaescu <dann@godzilla.ICS.UCI.EDU> writes:
  > 
  > > 
  > > Hi!
  > > 
  > > Here is a small cleanup for dwarf2. 
  > > A similar one was done for GCC as shown in: 
  > > 
  > >  http://gcc.gnu.org/ml/gcc-patches/2001-02/msg00856.html
  > > 
  > > and Jason Merill asked to do a similar one for gdb. 
  > > 
  > > Here it is, it's nothing else than copying the similar changes from
  > > GCC. 
  > > The patch is against gdb+dejagnu-20010215
  > > 
  > > For include/elf/ChangeLog
  > > 
  > > 2001-02-15  Dan Nicolaescu  <dann@ics.uci.edu>   
  > > 
  > >         * dwarf2.def: New file.
  > >    
  > >         * dwarf2.h: (enum dwarf_tag, enum dwarf_form,               
  > >         enum dwarf_attribute, enum dwarf_location_atom,
  > >         enum dwarf_type): Use the dwarf2.def definitions.                
  > > 
  > > For gdb/ChangeLog
  > >    
  > >         * dwarf2read.c (dwarf_cfi_name):
  > >         (dwarf_stack_op_name): 
  > >         (dwarf_tag_name):
  > >         (dwarf_attr_name):
  > >         (dwarf_form_name):                                           
  > >         (dwarf_type_encoding_name): Constify the return value, 
  > >         use the dwarf2.def definitions.
  > >    
  > >         * Makefile.in (dwarf2read.o): Add missing dependecy to
  > >         elf/dwarf2.h,  depend on elf/dwarf2.def.
  > > 


  reply	other threads:[~2001-02-16 14:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-15 16:18 Dan Nicolaescu
2001-02-16  9:02 ` Jim Blandy
2001-02-16 14:45   ` Dan Nicolaescu [this message]
2001-02-16 15:15     ` Jim Blandy
2002-06-20 11:12     ` Jim Blandy
2002-06-20 11:10 ` [very old] " Jim Blandy
2002-06-20 14:11   ` Andrew Cagney
2002-06-20 17:36   ` Elena Zannoni
2002-06-21 12:20     ` Jim Blandy
2002-06-21 16:46       ` Jason Merrill
2002-06-21 16:51         ` DJ Delorie
2002-06-21 17:01         ` DJ Delorie
2002-06-21 18:14           ` Jim Blandy
2002-06-21 20:07             ` Andrew Cagney
2002-06-21 19:41       ` Elena Zannoni

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=200102161444.aa08963@gremlin-relay.ics.uci.edu \
    --to=dann@godzilla.ics.uci.edu \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jason@redhat.com \
    --cc=jimb@zwingli.cygnus.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