The call_intrinsic op allows us to call LLVM intrinsics from the LLVMDialect without implementing a new op every time.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
nice
mlir/include/mlir/Dialect/LLVMIR/LLVMIntrinsicOps.td | ||
---|---|---|
683–685 | This is the new style for headers (LLVM dialect is very old!) | |
686 | can you name this LLVM_CallIntrinsicOp? It affects the name of the C++ class | |
686 | can you add a summary and description field to document the op? | |
692–694 | ||
701 | can you outline this to a C++ file? I think you can add a function to mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp where the generated code gets pasted |
mlir/include/mlir/Dialect/LLVMIR/LLVMIntrinsicOps.td | ||
---|---|---|
701 | I moved a bunch of it to getOverloadedDeclaration, let me know what you think |
mlir/include/mlir/Dialect/LLVMIR/LLVMIntrinsicOps.td | ||
---|---|---|
697 | An intrinsic that doesn't exist shouldn't cause the exporter to assert. Can you have it fail gracefully with an error? | |
703 | please drop trivial braces | |
mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp | ||
271 | please drop trivial braces | |
mlir/test/Dialect/LLVMIR/call-intrin.mlir | ||
15 | What happens when you try to export an intrinsic that doesn't exist on all systems? I'm worried this test might fail on some systems |
Very exciting Lily, thank you for implementing this!
mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp | ||
---|---|---|
266 | Plz only eval getNumOperands once per iteration and prefer preincrement: for (size_t i = 0, e = opInst.getNumOperands(); i != e; ++i) It is a micro thing but helps with consistency. | |
283 | Do you need the llvm:: namespace qualifiers in the .cpp file? I think they can all be dropped | |
283 | Can you pass Table directly into matchIntrinsicSignature? I think they implicitly convert and you can get rid of TableRef | |
mlir/test/Dialect/LLVMIR/call-intrin.mlir | ||
15 | I think it will always work but am not sure, how do we test this? Maybe add a weird target intrinsic that you don't have configured to check? |
Fix error messages + comments
mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp | ||
---|---|---|
283 | I do need the llvm:: namespace qualifiers unfortunately; a lot of other functions in this file use them too. :( And I'm not sure why, but if I try to pass Table in directly, it doesn't compile with this error-- /home/lily/llvm-project/mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp:283:52: error: non-const lvalue reference to type 'ArrayRef<llvm::Intrinsic::IITDescriptor>' cannot bind to a value of unrelated type 'SmallVector<llvm::Intrinsic::IITDescriptor, 8>' if (llvm::Intrinsic::matchIntrinsicSignature(FT, Table, There are other functions that called matchIntrinsicSignature like this as well | |
mlir/test/Dialect/LLVMIR/call-intrin.mlir | ||
15 | I'm not 100% sure what the behavior is-- if the intrinsic isn't on a particular machine then then it might just return 0 when it tries to get the intrinsic. I can change this to a different test | |
15 | Earlier today I was trying to use some intrinsics that were listed in llvmint, and getting back 0 for the id of those intrinsics. Turns out they were ones that weren't in ""LLVMConvertibleLLVMIRIntrinsics.inc". I'm not sure if "LLVMConvertibleLLVMIRIntrinsics.inc" is dependent on the target or if it's just a static list that's the same across all backends. |
I do need the llvm:: namespace qualifiers unfortunately; a lot of other functions in this file use them too. :(
Ok!
mlir/include/mlir/Dialect/LLVMIR/LLVMIntrinsicOps.td | ||
---|---|---|
689 | To provide a similar summary to the normal call op. | |
690–692 | ||
698–699 | ||
700–701 | How does success translate to error propagating correctly? | |
701 | I would move all of this out of line if possible. | |
706–708 | ||
718 | Drop the newline here. | |
725–727 | I would actually advocate for not having this on the op definition, because it requires having LLVM IR linked and available (which I don't think we want really in the LLVM dialect, even if it currently does now). | |
mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp | ||
261–262 | Can you document this method? The contract seems specific, also can you have a more specific operation type for opInst? | |
286 | Do you have tests for these error cases? | |
286–287 | ||
290–293 |
Comments + add more tests
mlir/include/mlir/Dialect/LLVMIR/LLVMIntrinsicOps.td | ||
---|---|---|
700–701 | It actually should be failure(), my error checking was not quite right and it was working for failure() and not success() | |
725–727 | OK, I can inline it | |
mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp | ||
261–262 | It looks like opInst is the exact same thing as op, so I can actually just get rid of opInst. | |
286 | I added a test for intrinsic type is not a match. For the variadic-ness one, I can't find a variadic intrinsic, so I didn't add a test. It seems like variadic intrinsics are uncommon, though, and I'm not sure how to support them. I updated the error message to say that we don't support calling variadic intrinsics. |
As something that better enables scaling to the many intrinsics, this LGTM conceptually.
mlir/include/mlir/Dialect/LLVMIR/LLVMIntrinsicOps.td | ||
---|---|---|
687–688 | Could you sink these below the summary+description? Those fields should generally always be at the top. | |
mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp | ||
269–271 | Can you do something like: | |
280 | Please use camelCase for variable names. Same below. | |
284 | Do you need this temporary variable? Can you just pass Table inline? | |
286 | You could try llvm.localescape which is variadic IIRC. There are a few others as well. | |
286–287 | The return op.emitOpError still looks unresolved? | |
312–313 |
add variadic test + remove variadic check since it's unneeded
mlir/lib/Target/LLVMIR/Dialect/LLVMIR/LLVMToLLVMIRTranslation.cpp | ||
---|---|---|
286 | Thanks! I added a test for localescope, and it seems like things are working fine for variadic localescope, so I'm just going to remove the check. I don't think it's possible to trigger it. |
This is the new style for headers (LLVM dialect is very old!)