On Wed, Sep 11, 2013 at 01:49:46PM +0100, Gary Benson wrote:
> Jakub Jelinek wrote:
> > cp-demangle.c isn't used just in libiberty, where using hashtab,
> > xcalloc, XNEW etc. is fine, but also in libsupc++/libstdc++, where
> > none of that is fine. That is why cp-demangle.c only uses
> > e.g. rea
Jakub Jelinek wrote:
> cp-demangle.c isn't used just in libiberty, where using hashtab,
> xcalloc, XNEW etc. is fine, but also in libsupc++/libstdc++, where
> none of that is fine. That is why cp-demangle.c only uses
> e.g. realloc, checks for allocation failures and propagates those to
> the call
Hi,
On 09/10/2013 05:34 PM, Jakub Jelinek wrote:
On Wed, Sep 04, 2013 at 03:29:43PM +0100, Gary Benson wrote:
I've added the result to the demangler test suite, but I know of
no way to check the validity of the demangled symbol other than by
inspection (and I am no expert here!) If anybody kno
On 09/10/2013 08:38 PM, Jakub Jelinek wrote
Agreed, can you please revert it?
Sure, I'll do that momentarily.
Paolo.
On Tue, Sep 10, 2013 at 08:36:02PM +0200, Paolo Carlini wrote:
> On 09/10/2013 05:34 PM, Jakub Jelinek wrote:
> >On Wed, Sep 04, 2013 at 03:29:43PM +0100, Gary Benson wrote:
> >>I've added the result to the demangler test suite, but I know of
> >>no way to check the validity of the demangled symbol
On Wed, Sep 04, 2013 at 03:29:43PM +0100, Gary Benson wrote:
> I've added the result to the demangler test suite, but I know of
> no way to check the validity of the demangled symbol other than by
> inspection (and I am no expert here!) If anybody knows a way to
> check this then please let me kno
OK, thanks.
Jason
Hi all,
d_print_comp maintains a certain amount of scope across calls (namely
a stack of templates) which is used when evaluating references in
template argument lists. If such a reference is later used from a
subtitution then the scope in force at the time of the substitution is
used. This appe
