On 5/13/2014 4:40 PM, Richard Henderson wrote: > On 05/13/2014 02:32 PM, Tom Musta wrote: >> Here is the -d op output. What does the "mov_i32 tmp0,r4" op mean >> when r4 is an i64? > > It's supposed to be the truncate. > > I believe I know what's going on. I've introduced this bug yesterday, of > course. Thomas Huth bisected a problem with an s390 host, and I strongly > suspect that it's the same bug. (I haven't been able to reserve an s390 build > system today to verify.) > > Try the tree prior to af3cbfbe8018ccc16fb3a0048e928f66f0d05e87 and see > if things work. > > Ho hum. Patch coming soon. > > > r~ >
Yes ... that worked ... sort of. I had to back up prior to this: fdd8ec71847b5167a4be524c2d22d186fc3b6e3a is the first bad commit to get to a point that built. Thanks, Peter and Richard for the help.
