> > Compiling the go tool chain with sse2 under VMware yields broken > tools, and building with GO386=387, consistently breaks the tests. On > bare metal, all tests except net/http pass most of the time. When a > test fails I get the following errors:
which tests does it break? ?c compile -0. as 0 (which is incorrect), and print(2)'s %g and %f print -0. as 0. could this or other bits of non-ieee conformance in the system be the real issue? > From the test: > <test> <pid>: suicide: sys: trap: fault write addr=0xfffffffc pc=0x0001e6ea > panic: runtime error: index out of range i can't imagine how bad sse would lead to accessing address -4. this looks like the problem rob fixed the other week. - erik
