> > A fix has been committed, but there's still a problem on loongson with > > libm updated:
[...] > This is definitely a problem in gdtoa. The values are always computed > the same, but do not get printed correctly, as shown by this modified > test program. Both lines should print 0.606531 for the long doubles, but > don't always; this smells like an uninitialized value somewhere. Well, it turned out this was caused by the program stack being aligned to an 8 byte boundary, instead of a 16 byte boundary, causing long double variables on the stack to be misaligned 50% of the time. This has been fixed now. Miod
