On Mon, Mar 17, 2025 at 11:34:36AM -0500, Robert Dubner wrote:
> > This would be a major problem.
> > Generally, we want to allow even cross-testing from 32-bit
> architectrures,
> > so they'd better fit into 3GB of memory at most.
>
> At the present time, the executables cannot be compiled for 32-bit
> architectures, so for now I would think that is moot.
But they should, at least e.g. in i686-linux -> x86_64-linux etc.
cross-compilers.
In any case, usually people test with make -jN check for large N and
if testing of a single language would need gigabytes of memory that
would cause problems for the parallel testing.
> A directive that says, "Compare the executable's output to a file" would
> be glorious. I have trouble understanding how the project has existed
> through eight American presidential administrations and the dissolution of
> the Soviet Union without that capability.
The answer is easy, out of more than 100000 tests in gcc/testsuite/
only 727 actually look at the output (have dg-output directives) and
there is 5.5 dg-output directives per test that does use those on average.
Most of the testsuite either looks for compilation errors or warnings
from the compiler or runs tests and just expect they don't abort/crash
or compiles without static assertion failures etc.
I/O is not the main thing being tested and even if it is tested, often
tests use something like sprintf/snprintf or C++ I/O into strings rather
than file streams.
Jakub
