[IAS] Teach -cc1as about the 'target-abi' option.

[tomatabacu]

Summary

When using the IAS from clang, the 'target-abi' option gets passed to cc1as, but cc1as doesn't know about it and gives an "unknown argument" error.

This is fixed by adding the 'CC1AsOption' flag to the 'target-abi' option in CC1Options.td.

[tomatabacu]

The testing probably needs improving, seeing as it's only covering the MIPS ABIs, but I'd like to know if I've approached this correctly first.

[atanasyan]

I would try to keep the mips-integrated-as.s unchanged and write another test case where explicitly invoke the clang with -cc1as and -target-abi options. That allows to check that the -target-abi option is not rejected and really affects output.

[tomatabacu]

Made a new test which uses cc1as directly, as suggested by Simon.

[dsanders]

LGTM

[echristo]

I don't think it's necessary to test that each ABI isn't ignored. Just one will be fine.

-eric

[tomatabacu]

Removed unnecessary target-abi checks.

[echristo]

Comment inline.

test/Driver/target-abi-cc1as.s

6

This means you can just do a CHECK line here.

[tomatabacu]

Replied to inline comment.

test/Driver/target-abi-cc1as.s

6

Fixed in the recommit r231363 (which happened because of buildbot failures).

include/clang/Driver/CC1Options.td

 let Flags = [CC1Option, CC1AsOption, NoDriverOption] in {
 
 def target_cpu : Separate<["-"], "target-cpu">,
   HelpText<"Target a specific cpu type">;
 def target_feature : Separate<["-"], "target-feature">,
   HelpText<"Target specific attributes">;
 def triple : Separate<["-"], "triple">,
   HelpText<"Specify target triple (e.g. i686-apple-darwin9)">;
+def target_abi : Separate<["-"], "target-abi">,
+  HelpText<"Target a particular ABI type">;
 
 }
 
-def target_abi : Separate<["-"], "target-abi">,
-  HelpText<"Target a particular ABI type">;
 def target_linker_version : Separate<["-"], "target-linker-version">,
   HelpText<"Target linker version">;
 def triple_EQ : Joined<["-"], "triple=">, Alias<triple>;
 def mfpmath : Separate<["-"], "mfpmath">,
   HelpText<"Which unit to use for fp math">;
 
 //===----------------------------------------------------------------------===//
 // Analyzer Options

test/Driver/target-abi-cc1as.s

+// Check if -cc1as knows about the 'target-abi' argument.
+
+// RUN: %clang -cc1as -triple mips--linux-gnu -filetype obj -target-cpu mips32 -target-abi o32 %s 2>&1 | \
+// RUN:   FileCheck --check-prefix=ABI-O32 %s
+// ABI-O32-NOT: clang -cc1as: error: unknown argument: '-target-abi'
+
+// RUN: %clang -cc1as -triple mips--linux-gnu -filetype obj -target-cpu mips32 -target-abi eabi %s 2>&1 | \
+// RUN:   FileCheck --check-prefix=ABI-EABI32 %s
+// ABI-EABI32-NOT: clang -cc1as: error: unknown argument: '-target-abi'
+
+// RUN: %clang -cc1as -triple mips64--linux-gnu -filetype obj -target-cpu mips64 -target-abi n32 %s 2>&1 | \
+// RUN:   FileCheck --check-prefix=ABI-N32 %s
+// ABI-N32-NOT: clang -cc1as: error: unknown argument: '-target-abi'
+
+// RUN: %clang -cc1as -triple mips64--linux-gnu -filetype obj -target-cpu mips64 -target-abi n64 %s 2>&1 | \
+// RUN:   FileCheck --check-prefix=ABI-N64 %s
+// ABI-N64-NOT: clang -cc1as: error: unknown argument: '-target-abi'