@@ -0,0 +1,9 @@
+; RUN: mlir-translate -import-llvm -split-input-file %s | FileCheck %s
gysit wrote:
> To me, it would make sense if mlir-translate didn't care - it doesn't have to
> interpret these attributes, does it?
It doesn't do anything with them except f
@@ -0,0 +1,9 @@
+; RUN: mlir-translate -import-llvm -split-input-file %s | FileCheck %s
gysit wrote:
Interesting!
Did you build your LLVM with the x86 target enabled (besides Aarch64)? If not,
`mlir-translate` may indeed be fine with the attribute independent o
@@ -0,0 +1,7 @@
+// RUN: mlir-translate -mlir-to-llvmir %s | FileCheck %s
gysit wrote:
This may require x86-registered-target as well?
https://github.com/llvm/llvm-project/pull/96688
___
cfe-commits mailing list
cfe-co
@@ -0,0 +1,9 @@
+; RUN: mlir-translate -import-llvm -split-input-file %s | FileCheck %s
gysit wrote:
Should this test also be guarded with `REQUIRES: x86-registered-target`?
https://github.com/llvm/llvm-project/pull/96688
@@ -1796,6 +1797,10 @@ void
ModuleImport::processFunctionAttributes(llvm::Function *func,
attr.isStringAttribute())
funcOp.setTargetCpuAttr(StringAttr::get(context, attr.getValueAsString()));
+ if (llvm::Attribute attr = func->getFnAttribute("tune-cpu");
+ att
@@ -1796,6 +1797,10 @@ void
ModuleImport::processFunctionAttributes(llvm::Function *func,
attr.isStringAttribute())
funcOp.setTargetCpuAttr(StringAttr::get(context, attr.getValueAsString()));
+ if (llvm::Attribute attr = func->getFnAttribute("tune-cpu");
+ att
