================
@@ -2862,6 +2845,46 @@ def CIR_VTableGetVirtualFnAddrOp :
CIR_Op<"vtable.get_virtual_fn_addr", [
}];
}
+//===----------------------------------------------------------------------===//
+// VTableGetTypeInfoOp
+//===----------------------------------------------------------------------===//
+
+def CIR_VTableGetTypeInfoOp : CIR_Op<"vtable.get_type_info", [
+ Pure
+]> {
+ let summary = "Get the address of the type_info from the vtable";
+ let description = [{
+ The `vtable.get_type_info` operation retreives the address of the dynamic
+ type_info/rtti object from an object's vtable. This is an ABI independent
+ abstraction of this operation.
+
+ The `vptr` operand must be a `!cir.ptr<!cir.vptr>` value, which would
+ have been returned by a previous call to `cir.vtable.get_vptr`.
+
+ The return type is a loadable pointer to a `type_info` struct.
+
+ Example:
+ ```mlir
+ %5 = cir.vtable.get_vptr %2 : !cir.ptr<!rec_A> -> !cir.ptr<!cir.vptr>
+ %6 = cir.load align(8) %5 : !cir.ptr<!cir.vptr>, !cir.vptr
+ %7 = cir.vtable.get_type_info %6 : !cir.vptr ->
!cir.ptr<!cir.ptr<!rec_std3A3Atype_info>>
----------------
erichkeane wrote:
I don't mind either way? I don't really have a preference though. I can wrap
it if you'd like, it seems easy enough to do.
https://github.com/llvm/llvm-project/pull/184449
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
