https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88409
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-12-07
Ever confirmed|0 |1
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Nick Clifton from comment #1)
> Created attachment 45184 [details]
> 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...
This will cause a regression since this input will fail now.
