Hi all, the performance of the parser changed a bit. The output of the current version in 1.6.0 RC2 is different from the output of the 1.5.3 release. Even tough there shouldn't been any difference as far as I can see.
The question of what caused that difference came up and I started to bisect it. Here are my results so far: 1655561 -> 1fe53c0aeaae1eb978dbb83f34b13944f2692b1f (head) 1591889 -> 1fe53c0aeaae1eb978dbb83f34b13944f2692b1f (5/2/14) 1576093 -> 1fe53c0aeaae1eb978dbb83f34b13944f2692b1f (3/10/14) 1574819 -> 1fe53c0aeaae1eb978dbb83f34b13944f2692b1f (3/6/14) 1574524 -> 1fe53c0aeaae1eb978dbb83f34b13944f2692b1f (3/5/14) 1574505 -> 93c912e100932384465ec740d144a94656f214d3 (3/5/14) 1573000 -> 93c912e100932384465ec740d144a94656f214d3 (2/28/14) 1569434 -> 93c912e100932384465ec740d144a94656f214d3 (2/18/14) 1569285 -> 93c912e100932384465ec740d144a94656f214d3 (2/18/14) 1554795 -> 93c912e100932384465ec740d144a94656f214d3 (1/2/14) 1463979 -> 93c912e100932384465ec740d144a94656f214d3 (1.5.3) The first column is the svn revision, the second column the hash of the output data and in the parenthesis is the date of the revision or the version. The change in the code which caused the difference happened in 1574524. I had a quick look there and couldn't see within a few minutes what caused the issue. I will probably again use a more systematic approach to find the exact change in that commit that causes the difference. Jörn