On Fri, Mar 18, 2011 at 14:05, Andreas Schwab wrote:
> Diego Novillo writes:
>
>> Thanks, but I don't think match_max affects this. It's the output
>> from the compiler that is being truncated.
>
> I don't see that problem on powerpc-linux (and I couldn't find any such
> failure on gcc-testresul
Diego Novillo writes:
> Thanks, but I don't think match_max affects this. It's the output
> from the compiler that is being truncated.
I don't see that problem on powerpc-linux (and I couldn't find any such
failure on gcc-testresults).
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Ke
On Fri, Mar 18, 2011 at 11:43, Joseph S. Myers wrote:
> There are a couple of places in DejaGnu's remote.exp that compare numbers
> of bytes with 512000; try increasing those to a much bigger figure, say
> 512.
Thanks. Given that my output is truncated at ~1Mb, I'm not sure if
this will hel
On Fri, Mar 18, 2011 at 11:55, Andreas Schwab wrote:
> Diego Novillo 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. Wit
On Fri, 18 Mar 2011, Diego Novillo wrote:
> I don't really know why the others don't fail, but I will take a look.
> In this particular case, the output is truncated after 1,032,134
> bytes are printed. So I can only speculate that no other tests
> generate more than this number of bytes in outp
Diego Novillo 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.
W
On Fri, Mar 18, 2011 at 11:40, Paolo Carlini wrote:
> On 03/18/2011 04:35 PM, Diego Novillo wrote:
>>
>> I don't really know why the others don't fail, but I will take a look.
>> In this particular case, the output is truncated after 1,032,134
>> bytes are printed. So I can only speculate that n
On 03/18/2011 04:35 PM, Diego Novillo wrote:
I don't really know why the others don't fail, but I will take a look.
In this particular case, the output is truncated after 1,032,134
bytes are printed. So I can only speculate that no other tests
generate more than this number of bytes in output.
On Fri, Mar 18, 2011 at 11:30, Paolo Carlini wrote:
> Hi
>>
>> 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 fo
Hi
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,
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
11 matches
Mail list logo