From: Tom Tromey <tromey@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Add support for imported declaration and correct search order
Date: Wed, 03 Mar 2010 22:00:00 -0000 [thread overview]
Message-ID: <m38wa93w28.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B8ED7C2.6030804@redhat.com> (Sami Wagiaalla's message of "Wed, 03 Mar 2010 16:42:26 -0500")
>>>>> "Sami" == Sami Wagiaalla <swagiaal@redhat.com> writes:
Sami> 2010-03-03 Sami Wagiaalla <swagiaal@redhat.com>
Sami> PR c++/7936:
Getting close...
Sami> +cp_add_using_directive (const char *dest,
Sami> + const char *src,
Sami> + const char *alias,
Sami> + const char *declaration,
Sami> struct obstack *obstack)
[...]
Sami> + if (declaration != NULL)
Sami> + new->declaration = savestring (declaration, strlen (declaration));
obsavestring
Does the duplicate exclusion logic here need to be updated to account
for the new field?
Sami> @@ -3448,23 +3448,32 @@ read_import_statement (struct die_info *die, struct dwarf2_cu *cu)
Sami> + canonical_name = (char *) imported_name_prefix;
I don't think you should need to cast away const in this function.
There is some other way to make it work, like having a non-const
temporary hold the result of alloca.
Sami> + else
Sami> + {
Sami> + canonical_name = alloca (strlen (imported_name) + 1);
Sami> + strcpy (canonical_name, imported_name);
Sami> + }
I think this is a pointless copy, just do canonical_name = imported_name.
thanks,
Tom
next prev parent reply other threads:[~2010-03-03 22:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 20:17 Sami Wagiaalla
2010-02-25 21:50 ` Tom Tromey
2010-02-25 22:42 ` Jan Kratochvil
2010-02-26 20:11 ` Tom Tromey
2010-03-03 21:46 ` Sami Wagiaalla
2010-03-03 22:00 ` Tom Tromey [this message]
2010-03-08 16:39 ` Sami Wagiaalla
2010-03-08 18:58 ` Tom Tromey
2010-03-09 18:21 ` Sami Wagiaalla
2010-03-09 18:27 ` Tom Tromey
2010-03-23 20:31 ` Ulrich Weigand
2010-03-23 20:51 ` Sami Wagiaalla
2010-03-23 21:35 ` Ulrich Weigand
2010-03-29 14:48 ` Sami Wagiaalla
2010-03-29 17:27 ` Tom Tromey
2010-03-29 17:23 ` Sami Wagiaalla
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=m38wa93w28.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=swagiaal@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