On Sun, Dec 01, 2024 at 12:32:55PM +0100, Georg-Johann Lay wrote:
> Am 01.12.24 um 05:45 schrieb Maciej W. Rozycki:
> > On Sat, 30 Nov 2024, Georg-Johann Lay wrote:
> >
> > > The gcc.c-torture/execute/memcpy-a[1248].c tests consumed more time
> > > than the whole rest of the test suite, just to come up with
> > > a "memory full" even at -Os. Skipped thusly.
> >
> > As a matter of interest, is the timeout/memory exhaustion observed with
> > host compilation or target execution?
>
> It happens during link, when the linker observes that the memory regions
> won't fit:
>
> .../avr/bin/ld: memcpy-a8.elf section `.text' will not fit in region `text'
> .../avr/bin/ld: address 0x82c174 of memcpy-a8.elf section `.data' is not
> within region `data'
> .../avr/bin/ld: address 0x82c17c of memcpy-a8.elf section `.bss' is not
> within region `data'
> .../avr/bin/ld: region `text' overflowed by 245074 bytes
> collect2: error: ld returned 1 exit status
The memory overflow should be caught by ${tool}_check_unsupported_p.
Even without this patch, the testsuite should mark the tests as
UNSUPPORTED and not FAIL for avr.
Compilation takes much host time for other targets too.
On native x86_64-pc-linux-gnu:
$ time make check-gcc-c RUNTESTFLAGS="execute.exp=memcpy-a*.c"
# of expected passes 56
real 8m37,778s
user 8m29,895s
sys 0m5,805s
Should these tests instead be gated by "run_expensive_tests"?
Regards
Dimitar
