https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88409
Nick Clifton <nickc at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at gcc dot gnu.org
--- Comment #1 from Nick Clifton <nickc at gcc dot gnu.org> ---
Created attachment 45184
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45184&action=edit
Proposed patch
*sigh* Yes, I forgot to run the libiberty testsuite, and of course
there is one test that actually breaches the demangling limit.
The attached patch resolves the problem by adding a --no-recurse-limit
option to the demangler testser and then using it for the problematic
test case. I felt that this was a better solution than raising the
recursion limit, as it means that the limit detecting code will actually
be exercised by the testsuite.
Currently waiting for review of the patch...
