> On Dec 8, 2014, at 08:21 , David Kastrup <[email protected]> wrote: > > Masamichi HOSODA <[email protected]> writes: > >>> I agree that changing the algorithms is preferred; I didn’t mean to >> suggest otherwise. But if that’s not going to happen overnight, and >> there is a way to mitigate the problem in the meantime without >> touching the code, the people affected would value it. >> >> I tried "-mfpmath=sse -msse2". >> It worked fine. bad_alloc didn't occur. >> Correct PDF was generated. >> >> It can be a workaround until changing the algorithms. > > It's not architecture independent. And may blow up for other reasons.
But it’s good to know that the problem was floating point and not memory corruption, so thanks for testing it. — Dan _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
