On Fri, Mar 18, 2011 at 11:55, Andreas Schwab <sch...@redhat.com> wrote: > Diego Novillo <dnovi...@google.com> writes: > >> Is there a way to increase dejagnu's buffering? > > expect(1): > > match_max [-d] [-i spawn_id] [size] > defines the size of the buffer (in bytes) used internally by > expect. With no size argument, the current size is returned. > > With the -d flag, the default size is set. (The initial default > is 2000.) With the -i flag, the size is set for the named spawn > id, otherwise it is set for the current process.
Thanks, but I don't think match_max affects this. It's the output from the compiler that is being truncated. I modified conformance.exp with a match_max value 10x the limit I need, but the failures are still there: Index: testsuite/libstdc++-dg/conformance.exp =================================================================== --- testsuite/libstdc++-dg/conformance.exp (revision 171068) +++ testsuite/libstdc++-dg/conformance.exp (working copy) @@ -21,6 +21,8 @@ # Initialization. dg-init +match_max -d 10000000 + # Build the support objects. v3-build_support Running <bld>/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... 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) The output is clearly truncated, right before the first 'PASS' result, I see: [ ... ]/x86_64-unknown-linux-gnu/libstdc++-v3/include/decimal/decimal.h:83:3: note: std::decimal::decimal32& std::decimal::decimal32::operator/=(long int)^M /usr/local/google/hom <<<< TRUNCATED PASS: decimal/mixed-mode_neg.cc (test for errors, line 43) PASS: decimal/mixed-mode_neg.cc (test for errors, line 44) Diego.
