Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@streamline-computing.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: patches <gdb-patches@sources.redhat.com>
Subject: Re: Dwarf2 Producer info
Date: Wed, 21 Jul 2004 07:12:00 -0000	[thread overview]
Message-ID: <1090394885.21483.134.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com> (raw)
In-Reply-To: <20040721000823.GA10146@nevyn.them.org>


Fine by me -- in fact, even the null setting isn't needed now I've found
the bit that ensures the cu is cleared during allocation (do you
agree?).

So here goes:

2004-07-20  David Lecomber  <dsl@sources.redhat.com>

	* dwarf2read.c (read_file_scope): Set producer if attribute 
	present.


Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.156
diff -p -r1.156 dwarf2read.c
*** dwarf2read.c	6 Jul 2004 19:29:30 -0000	1.156
--- dwarf2read.c	21 Jul 2004 07:07:03 -0000
*************** struct dwarf2_cu
*** 262,267 ****
--- 262,269 ----
    enum language language;
    const struct language_defn *language_defn;
  
+   const char* producer;
+ 
    /* The generic symbol table building routines have separate lists
for
       file scope symbols and all all other scopes (local scopes).  So
       we need to select the right one to pass to add_symbol_to_list().
*************** read_file_scope (struct die_info *die, s
*** 2362,2367 ****
--- 2364,2373 ----
        set_cu_language (DW_UNSND (attr), cu);
      }
  
+   attr = dwarf2_attr (die, DW_AT_producer, cu);
+   if (attr) 
+     cu->producer = DW_STRING (attr);
+   
    /* We assume that we're processing GCC output. */
    processing_gcc_compilation = 2;
  #if 0

On Wed, 2004-07-21 at 01:08, Daniel Jacobowitz wrote:
> On Wed, Jul 21, 2004 at 12:56:07AM +0100, David Lecomber wrote:
> > 
> > > Is set_cu_producer going to do anything else?  Otherwise I don't see
> > > the point of the wrapper function.
> > 
> > Hi Dan,
> > 
> > Not in the immediately foreseeable future, but I can imagine a situation
> > where the producer is matched with some known producer strings and an
> > enumerated constant is stored instead; if that ever happens, it will be
> > better if there's one setter.
> 
> There will still be only one setter; let's drop the useless wrapper,
> unless one of the dwarf2 maintainers feels otherwise.


  reply	other threads:[~2004-07-21  7:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 22:14 David Lecomber
2004-07-20 23:18 ` Daniel Jacobowitz
2004-07-20 23:40   ` David Lecomber
2004-07-21  0:09     ` Daniel Jacobowitz
2004-07-21  7:12       ` David Lecomber [this message]
2004-07-21 13:25         ` Daniel Jacobowitz
2004-07-28 19:05         ` Jim Blandy
2004-07-26 20:55 ` [RFA] Dwarf2 Producer info (dwarf2read.c) David Lecomber
2004-07-29 10:28   ` David Lecomber
2004-07-29 19:25     ` 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=1090394885.21483.134.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com \
    --to=david@streamline-computing.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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