https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95720
--- Comment #4 from Andrea Corallo <andrea.corallo at arm dot com> --- "aoliva at gcc dot gnu.org" <gcc-bugzi...@gcc.gnu.org> writes: > --- Comment #3 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- > akrl, any clue as to where this .out is coming from in your runs? I get .exe > in my arm test runs; I don't see anything that selects .out, only .exe; and > the > driver disregards the .exe suffix in executable output, regardless of > platform, > when recognizing that the single source has the same basename as the linker > output. Hi Alexandre, Apologies I guess the provided example was not the best. Here what I've specifically for the mentioned testcase, this is the compiler invocation: .../build/gcc/xgcc -B.../build/gcc/ .../src/gcc/gcc/testsuite/gcc.target/arm/memset-inline-1.c gcc_tg.o -march=armv8.1-m.main -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers -fdiagnostics-color=never -fdiagnostics-urls=never -save-temps -O2 -fno-inline -ffat-lto-objects -fno-ident -specs=rdimon.specs -Wa,-mno-warn-deprecated -Wl,-Ttext-segment=0x00500000 -Wl,-wrap,exit -Wl,-wrap,_exit -Wl,-wrap,main -Wl,-wrap,abort -lm -o ./memset-inline-1.exe The assembly file generated is called 'memset-inline-1-memset-inline-1.s' but IIUC the expected one by proc 'scan-assembler-not' (scanasm.exp:92) is 'memset-inline-1.s' (I'm just printing $output_file). Hope it helps. Andrea
