This was caused by a a function called some-bfloatp that was recursing wrongly on rational expressions. I've just pushed a fix for that bug as commit [24090c]. With your test-case, the lu_factor call now just takes an awfully long time (I didn't wait for it to finish). I don't know whether that's a regression or whether it was always a big computation. If the former, then maybe you want to open a new bug for that: performance timings would probably be very helpful.
This was caused by a a function called
some-bfloatpthat was recursing wrongly on rational expressions. I've just pushed a fix for that bug as commit [24090c]. With your test-case, the lu_factor call now just takes an awfully long time (I didn't wait for it to finish). I don't know whether that's a regression or whether it was always a big computation. If the former, then maybe you want to open a new bug for that: performance timings would probably be very helpful.Related
Commit: [24090c]
Hi,
Thanks for the patch.
Previously it take about 20 minutes to run this file on a xeon at 3Ghz.
If I do not use crering, it run for a month without result
Bastien
I will test ASAP