Please sign in to comment.
dtest: Disable optimization of the compiled tests
GCC optimizes ever more enthusiastically: At version 4, even at -O2, it does so in ways that break these tests and that are increasingly difficult to prevent with code changes. Instead of increasing levels of trickery, just disable optimization. The specific problems we've had are: - pid/tst.args1 Notices that the arguments passed to go() are unused, and so doesn't actually pass them. - pid/tst.ret1, pid/tst.ret2 Notices that handle() calling go() is without side-effect, doesn't do it. - profile-n/tst.ufuncsort, java_api/tst.ProbeData, java_api/tst.FunctionLookup Notices that because fN is static, it doesn't need to use the normal i386 ABI and instead passes arg0 in %eax, rather than on the stack.
- Loading branch information...
Showing with 6 additions and 2 deletions.