[AIX][Test][ORC] Skip unsupported ORC C API tests on AIX

[hubert.reinterpretcast]

Summary

As mentioned before in D78813, currently the XCOFF backend does not support writing 64-bit object files, which the ORC JIT tests will try to exercise if we are on AIX. This patch disables the tests on AIX for now. This is consistent with what's been done, for example, regarding armv7.

[lhames]

Hi Hubert,

It would be better to just disable these tests on AIX for now. You can do that by extending the static bool isSupported(StringRef Triple) method to return false for AIX.

XCOFF backend does not support writing 64-bit object files...

Is there some other object format that the JIT should be selecting? Or is AIX not expected to produce JIT-linkable objects at all?

• Lang.

[hubert.reinterpretcast]

In D101971#2741103, @lhames wrote:

Hi Hubert,

It would be better to just disable these tests on AIX for now. You can do that by extending the static bool isSupported(StringRef Triple) method to return false for AIX.

Thanks. I'll update the patch to do this.

XCOFF backend does not support writing 64-bit object files...

Is there some other object format that the JIT should be selecting?

Not really. There's only XCOFF in its 32-bit and 64-bit variations. We're building LLVM as a 64-bit application, so I think XCOFF64 is the right object format to select.

Or is AIX not expected to produce JIT-linkable objects at all?

I'm not certain how capable it is at this time of producing JIT-linkable objects. We've been trying to enable functionality for building C/C++ applications using Clang on AIX (which we had set up to call out to the system assembler). The direct object code generation started out with XCOFF32 and we ended up building that out further and further without getting to the XCOFF64 side.

• Lang.

[hubert.reinterpretcast]

Address comments: Use isSupported

[lhames]

LGTM. Thanks Hubert!

llvm/unittests/ExecutionEngine/Orc/OrcCAPITest.cpp

 
 protected:
   static bool isSupported(StringRef Triple) {
     // TODO: Print error messages in failure logs, use them to audit this list.
     // Some architectures may be unsupportable or missing key components, but
     // some may just be failing due to bugs in this testcase.
     if (Triple.startswith("armv7") || Triple.startswith("armv8l"))
       return false;
+    llvm::Triple T(Triple);
+    if (T.isOSAIX() && T.isPPC64())
+      return false;
     return true;
   }
 
   static void materializationUnitFn() {}
 
   // Stub definition generator, where all Names are materialized from the
   // materializationUnitFn() test function and defined into the JIT Dylib
   static LLVMErrorRef