> Troy Heber is debugging this on alpha and he reports that rebuilding > ruby1.8 with gcc 4.1 fixes it. Also, downgrading to ruby1.8 1.8.4-1 > fixed it, which I attribute to the fact that this too used a > different version of gcc for the alpha build. (Nobody has checked > whether any of this is also true on arm.)
Further info from Troy: gcc 4.0.3 with -fno-strict-aliasing also seems to fix this bug. I would strongly suggest adding -fno-strict-aliasing in any case (or _properly_ fixing the gcc warnings related to this), since it's quite possible that other bugs are also lurking due to this. Peter
signature.asc
Description: Digital signature
