Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org> writes: > On Thu, Mar 11, 2021 at 9:03 AM Alexandre Oliva <ol...@adacore.com> wrote: >> >> >> When vect.exp finds our configuration disables altivec by default, it >> disables the execution of vectorization tests, assuming the test >> hardware doesn't support it. >> >> Tests become just compile tests, but compile tests won't work >> correctly when additional sources are named, e.g. pr95401.cc, because >> GCC refuses to compile multiple files into the same asm output. >> >> With this patch, the default for when execution is not possible >> becomes link. >> >> >> This was regstrapped on x86_64-linux-gnu and ppc64-linux-gnu, and tested >> with a cross to a ppc64-vxworks7r2 with altivec disabled by default. I >> found fixing the handling of additional sources to e.g. compile each one >> separately, or perhaps just discard or reject additional sources for >> compile tests, to be a little too involved. >> >> So I'm leaning towards this proposed change, just extended to other >> platforms that also decay from run to compile rather than link, and thus >> run into this problem in g++.dg/vect/pr95401.cc. Would this be >> acceptable? > > I think that's OK.
+1 FWIW. It seems like an improvement anyway, since it makes it harder to forget an explicit dg-do compile in cases where it's needed. Richard
