[flang] fix errors in link*-main tests in D134821

[sunshaoce]

Summary

I tried to use %itanium_abi_triple, but it can only be used with -fc1 -triple.

Error info：

+ /home/tcwg-buildbot/worker/flang-aarch64-latest-gcc/build/bin/flang-new -fc1 -emit-obj /home/tcwg-buildbot/worker/flang-aarch64-latest-gcc/llvm-project/flang/test/Driver/link-f90-main.f90 -o /home/tcwg-buildbot/worker/flang-aarch64-latest-gcc/build/tools/flang/test/Driver/Output/link-f90-main.f90.tmp.o
+ : 'RUN: at line 10'
+ /home/tcwg-buildbot/worker/flang-aarch64-latest-gcc/build/bin/flang-new -target x86_64-unknown-linux-gnu /home/tcwg-buildbot/worker/flang-aarch64-latest-gcc/build/tools/flang/test/Driver/Output/link-f90-main.f90.tmp.o -o /home/tcwg-buildbot/worker/flang-aarch64-latest-gcc/build/tools/flang/test/Driver/Output/link-f90-main.f90.tmp.out -flang-experimental-exec
/usr/bin/ld: unrecognised emulation mode: elf_x86_64
Supported emulations: aarch64linux aarch64elf aarch64elf32 aarch64elf32b aarch64elfb armelf armelfb aarch64linuxb aarch64linux32 aarch64linux32b armelfb_linux_eabi armelf_linux_eabi
flang-new: error: linker command failed with exit code 1 (use -v to see invocation)

[awarzynski]

@sunshaoce I don't really understand what the issue with these tests is and the commit message does not explain that. IIUC, https://reviews.llvm.org/D134821 has caused the Flang buildbots to fail and that's what this patch is trying to address? It's impossible to verify ATM as the web UI is effectively frozen. I reverted that patch so that we can discuss the right solution without feeling under pressure of failing Ci jobs.

flang/test/Driver/link-c-main-aarch64.c

 /*
 Test that an object file with a C main function can be linked to an executable
 by Flang.
 
 For now, this test only covers the Gnu toolchain on Linux.
 
-REQUIRES: x86-registered-target || aarch64-registered-target || riscv64-registered-target
-REQUIRES: system-linux, c-compiler
+REQUIRES: aarch64-registered-target, system-linux, c-compiler
 
 RUN: %cc -c %s -o %t.o
-RUN: %flang -target x86_64-unknown-linux-gnu %t.o -o %t.out -flang-experimental-exec
+RUN: %flang -target aarch64-unknown-linux-gnu %t.o -o %t.out -flang-experimental-exec
 RUN: llvm-objdump --syms %t.out | FileCheck %s --implicit-check-not Fortran
 
 Test that it also works if the c-main is bundled in an archive.
 
 RUN: llvm-ar -r %t.a %t.o
-RUN: %flang -target x86_64-unknown-linux-gnu %t.a -o %ta.out -flang-experimental-exec
+RUN: %flang -target aarch64-unknown-linux-gnu %t.a -o %ta.out -flang-experimental-exec
 RUN: llvm-objdump --syms %ta.out | FileCheck %s --implicit-check-not Fortran
 */
 
 int main(void) {
     return 0;
 }
 
 /*
 CHECK-DAG: F .text {{[a-f0-9]+}} main
 CHECK-DAG: *UND* {{[a-f0-9]+}} _QQmain
 */

flang/test/Driver/link-c-main-x86.c

 /*
 Test that an object file with a C main function can be linked to an executable
 by Flang.
 
 For now, this test only covers the Gnu toolchain on Linux.
 
-REQUIRES: x86-registered-target || aarch64-registered-target || riscv64-registered-target
-REQUIRES: system-linux, c-compiler
+REQUIRES: x86-registered-target, system-linux, c-compiler
 
 RUN: %cc -c %s -o %t.o
 RUN: %flang -target x86_64-unknown-linux-gnu %t.o -o %t.out -flang-experimental-exec
 RUN: llvm-objdump --syms %t.out | FileCheck %s --implicit-check-not Fortran
 
 Test that it also works if the c-main is bundled in an archive.
 
 RUN: llvm-ar -r %t.a %t.o

flang/test/Driver/link-f90-main-aarch64.f90

 ! Test that a fortran main program can be linked to an executable
 ! by flang.
 !
 ! For now, this test only covers the Gnu toolchain on linux.
 
-!REQUIRES: x86-registered-target || aarch64-registered-target || riscv64-registered-target
-!REQUIRES: system-linux
+!REQUIRES: aarch64-registered-target, system-linux
 
 ! RUN: %flang_fc1 -emit-obj %s -o %t.o
-! RUN: %flang -target x86_64-unknown-linux-gnu %t.o -o %t.out -flang-experimental-exec
+! RUN: %flang -target aarch64-unknown-linux-gnu %t.o -o %t.out -flang-experimental-exec
 ! RUN: llvm-objdump --syms %t.out | FileCheck %s
 
 ! Test that it also works if the program is bundled in an archive.
 
 ! RUN: llvm-ar -r %t.a %t.o
-! RUN: %flang -target x86_64-unknown-linux-gnu %t.a -o %ta.out -flang-experimental-exec
+! RUN: %flang -target aarch64-unknown-linux-gnu %t.a -o %ta.out -flang-experimental-exec
 ! RUN: llvm-objdump --syms %ta.out | FileCheck %s
 
 end program
 
 ! CHECK-DAG: F .text {{[a-f0-9]+}} main
 ! CHECK-DAG: F .text {{[a-f0-9]+}} _QQmain
 ! CHECK-DAG: _FortranAProgramStart

flang/test/Driver/link-f90-main-x86.f90

 ! Test that a fortran main program can be linked to an executable
 ! by flang.
 !
 ! For now, this test only covers the Gnu toolchain on linux.
 
-!REQUIRES: x86-registered-target || aarch64-registered-target || riscv64-registered-target
-!REQUIRES: system-linux
+!REQUIRES: x86-registered-target, system-linux
 
 ! RUN: %flang_fc1 -emit-obj %s -o %t.o
 ! RUN: %flang -target x86_64-unknown-linux-gnu %t.o -o %t.out -flang-experimental-exec
 ! RUN: llvm-objdump --syms %t.out | FileCheck %s
 
 ! Test that it also works if the program is bundled in an archive.
 
 ! RUN: llvm-ar -r %t.a %t.o
 ! RUN: %flang -target x86_64-unknown-linux-gnu %t.a -o %ta.out -flang-experimental-exec
 ! RUN: llvm-objdump --syms %ta.out | FileCheck %s
 
 end program
 
 ! CHECK-DAG: F .text {{[a-f0-9]+}} main
 ! CHECK-DAG: F .text {{[a-f0-9]+}} _QQmain
 ! CHECK-DAG: _FortranAProgramStart