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? From my observation the optimisation level does not matter much for compilation times unless you use -O0, reducing the number of passes and code transformations applied. So whether it's at -O2 or -Os the time consumed does not change much. The resulting executables themselves take ~560KiB with a VAX target, the ultimate CISC machine which also has memory move and memory set hardware instructions contributing to size reduction, and ~1200KiB with a POWER9 target, a 64-bit RISC machine. I suppose the sizes will lie somewhere in between for the majority of our targets, and with smaller embedded ones the executables may not fit in the address space available. Maciej
