Re: [C++ PATCH] demangler fix

2014-05-07 Thread Jason Merrill
OK, thanks. Jason

[C++ PATCH] demangler fix

2014-05-07 Thread Gary Benson
Hi all, A patch I committed to libiberty last year [1, 2] caused a regression that caused the demangler to segfault on certain symbols [3, 4, 5, 6]. The attached patch fixes, and adds regression tests for all symbols referenced in those bugs. Ok to commit? Thanks, Gary -- http://gbenson.net/ [

Re: [2nd PING] [C++ PATCH] demangler fix (take 2)

2013-10-23 Thread Jason Merrill
On 10/08/2013 05:54 AM, Gary Benson wrote: diff --git a/test.c b/test.c I don't think we want to add this to the top level directory. :) Other than that, the patch is OK. Jason

[2nd PING] [C++ PATCH] demangler fix (take 2)

2013-10-08 Thread Gary Benson
Hi all, This is a resubmission of my previous demangler fix [1] rewritten to avoid using hashtables and other libiberty features. From the above referenced email: d_print_comp maintains a certain amount of scope across calls (namely a stack of templates) which is used when evaluating references

[PING] [C++ PATCH] demangler fix (take 2)

2013-09-27 Thread Gary Benson
Gary Benson wrote: > Hi all, > > This is a resubmission of my previous demangler fix [1] rewritten > to avoid using hashtables and other libiberty features. > > From the above referenced email: > > d_print_comp maintains a certain amount of scope across calls (namely > a stack of templates) whic

[C++ PATCH] demangler fix (take 2)

2013-09-17 Thread Gary Benson
Hi all, This is a resubmission of my previous demangler fix [1] rewritten to avoid using hashtables and other libiberty features. >From the above referenced email: d_print_comp maintains a certain amount of scope across calls (namely a stack of templates) which is used when evaluating references