On 28/01/2016 16:17, Phil Clayton wrote:
The values were indeed equal and the change to ASSERT(costMin >= userGCRatio); avoids the failure. I added code to print the values if they are equal and we get: costMin = 0.111111111111111104943205418749 userGCRatio = 0.111111111111111104943205418749 which is the nearest value to 1/9 for a double.
In case you're wondering which commit introduces the regression, it was d0815825. The previous commit 3ca17b4b does not show this problem. I looked at the log for just libpolyml/heapsizing.cpp and this change seemed the best candidate and got lucky.
Thanks. That's very useful. I've committed a fix.
David