Commit: Sync libiberty and add --no-recurse-limit option to binutils
Ian Lance Taylor via binutils
Fri Dec 7 18:54:00 GMT 2018
On Fri, Dec 7, 2018 at 8:07 AM Nick Clifton <email@example.com> wrote:
> Hi Alan,
> > make: Entering directory '/home/alan/build/gas/all/libiberty/testsuite'
> > FAIL at line 4429, options --format=gnu-v3:
> Oh fribble! Yes I forgot to check that the testsuite passed cleanly,
> and yes, I missed a case where the demangling limit should be turned off.
> Fixed by the attached patch which adds a --no-recurse-limit option to
> the demangler tester and uses it for the case that fails. (I did consider
> changing the demangling limit instead, but I thought that it would be
> better to have a test case that actually needs the limit to be turned off).
> Ian - is this OK for libiberty ?
> 2018-12-07 Nick Clifton <firstname.lastname@example.org>
> * testsuite/test-demangle.c (main): Add --no-recurse-limit option.
> * testsuite/demangle-expected: Use the --no-recurse-limit option
> for the test on line 4428.
Since this is apparently a real symbol from real code, can you find
out what the recursion limit would have to be to successfully demangle
More information about the Binutils