From: Daniel Jacobowitz <drow@false.org>
To: David Lecomber <david@streamline-computing.com>
Cc: patches <gdb-patches@sources.redhat.com>
Subject: Re: Dwarf2 Producer info
Date: Tue, 20 Jul 2004 23:18:00 -0000 [thread overview]
Message-ID: <20040720231756.GA8250@nevyn.them.org> (raw)
In-Reply-To: <1090362598.21483.108.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com>
On Tue, Jul 20, 2004 at 11:29:58PM +0100, David Lecomber wrote:
> Hi
>
> This is an obvious extension to plug a gap.
>
> I've some more changes to come that make use of this (specifically to
> take account of broken g77) and also fix some longstanding array issues,
> but I'm getting this easy one in the source before inflicting the
> complex one on the world.. if anyone has a sharper eye than me for the
> code formatting rules, please feel free to shout out!
I guess changing behavior based on producer is less gross than a lot of
our existing hacks...
> + const char* producer;
> +
"const char *"
> /* The generic symbol table building routines have separate lists
> for
Please use a mailer which does not line wrap patches.
> + static void set_cu_producer (const char*, struct dwarf2_cu *);
"const char *"
> + if (attr)
> + set_cu_producer (DW_STRING (attr), cu);
> + else
> + set_cu_producer(NULL, cu);
set_cu_producer (NULL, cu);
Is set_cu_producer going to do anything else? Otherwise I don't see
the point of the wrapper function.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-07-20 23:18 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 [this message]
2004-07-20 23:40 ` David Lecomber
2004-07-21 0:09 ` Daniel Jacobowitz
2004-07-21 7:12 ` David Lecomber
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=20040720231756.GA8250@nevyn.them.org \
--to=drow@false.org \
--cc=david@streamline-computing.com \
--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