On 26/04/2022 16:12, Jakub Jelinek wrote:
On Tue, Apr 26, 2022 at 03:43:13PM +0100, Richard Sandiford via Gcc-patches
wrote:
--- /dev/null
+++ b/gcc/testsuite/gcc.target/aarch64/pr105219-2.c
@@ -0,0 +1,29 @@
+/* { dg-do run } */
+/* { dg-options "-O3 -march=armv8.2-a -mtune=thunderx -fno-vect-cost-model" }
*/
+/* { dg-skip-if "incompatible options" { *-*-* } { "-march=*" } {
"-march=armv8.2-a" } } */
+/* { dg-skip-if "incompatible options" { *-*-* } { "-mtune=*" } {
"-mtune=thunderx" } } */
+/* { dg-skip-if "incompatible options" { *-*-* } { "-mcpu=*" } } */
I think this should be in gcc.dg/vect, with the options forced
for { target aarch64 }.
I think not just aarch64, doesn't it need some effective target that
the HW on which it is tested is ARM v8.2-a compatible plus that binutils
can assemble v8.2-a instructions?
Sure, it can be done in gcc.dg/vect too if those effective targets
aren't defined in aarch64.exp. But probably needs dg-additional-options
there instead of dg-options.
Jakub
For some reason I thought richi wasn't able to reproduce this on other
targets, but from my last read of the PR I think he was... Regardless
probably worth testing it for all targets for sure.
Question is how do I make it run for all targets but use target specific
options for each to try and trigger the original issue? Multiple
dg-additional-options with different target selectors?
Kind regards,
Andre
