I am getting several failures in decimal/mixed-mode_neg.cc: FAIL: decimal/mixed-mode_neg.cc (test for errors, line 195) FAIL: decimal/mixed-mode_neg.cc (test for errors, line 196) FAIL: decimal/mixed-mode_neg.cc (test for errors, line 197) FAIL: decimal/mixed-mode_neg.cc (test for errors, line 198) FAIL: decimal/mixed-mode_neg.cc (test for errors, line 199) FAIL: decimal/mixed-mode_neg.cc (test for errors, line 200) FAIL: decimal/mixed-mode_neg.cc (test for errors, line 201) FAIL: decimal/mixed-mode_neg.cc (test for errors, line 202) FAIL: decimal/mixed-mode_neg.cc (test for errors, line 203)
This test expects syntax errors in all these lines, and the compiler is indeed flagging them but the output from the compiler is so big that dejagnu truncates it. The testsuite never sees the error messages starting at line 195 (I can see the output truncated in libstdc++.log). Is there a way to increase dejagnu's buffering? This does not happen, if I simply run the build in a shallower build tree, but that is not a viable alternative. Any suggestions on how to address this, short of butchering this test? Thanks. Diego.
