On Mon, Apr 14, 2025 at 07:47:21PM +0200, Thomas Schwinge wrote:
> gcc/testsuite/
> * lib/gcc-dg.exp (${tool}_load): Polish 'dg-output-file' test
> logs.
> ---
> gcc/testsuite/lib/gcc-dg.exp | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/gcc/testsuite
Hi!
On 2025-04-13T17:15:05+0200, I wrote:
> On 2025-03-18T14:54:23+0100, Jakub Jelinek wrote:
>> The following patch offers [...] dg-output-file
>> directive where one can supply a text file with expected output
>
>> --- gcc/doc/sourcebuild.texi.jj 2025-03-11 09:18:21.750133577 +0100
>> +++
Hi!
On 2025-03-18T14:54:23+0100, Jakub Jelinek wrote:
> The following patch offers [...] dg-output-file
> directive where one can supply a text file with expected output
> --- gcc/doc/sourcebuild.texi.jj 2025-03-11 09:18:21.750133577 +0100
> +++ gcc/doc/sourcebuild.texi 2025-03-18 14:41:5
On Tue, 18 Mar 2025, Jakub Jelinek wrote:
> Hi!
>
> The COBOL tests has many tests which just dump emit lots of output
> to stdout and want to compare it against expected output.
> We have the dg-output directive, but if one needs more than dozens
> of lines in the output, adding hundreds of dg-o
Hi!
The COBOL tests has many tests which just dump emit lots of output
to stdout and want to compare it against expected output.
We have the dg-output directive, but if one needs more than dozens
of lines in the output, adding hundreds of dg-output directives to
each source uses too much memory an
