================
@@ -119,11 +119,8 @@ buildNewArgTypes(ArrayRef<mlir::Type> oldArgTypes,
newArgTypes.push_back(origTy);
break;
case ArgKind::Indirect:
- // byval and byref both use a pointer wire type. The attribute
- // distinction (llvm.byval vs llvm.byref) is applied in updateArgAttrs;
- // the call-site rewrite guards against byref separately because passing
- // a byref pointer from a CIR value requires the original alloca address,
- // which the rewriter does not yet track.
+ // byval and byref both use a pointer wire type. The llvm.byval vs
----------------
erichkeane wrote:
`wire` type? Is there a wire involved here? That term is usually used to
refer to 'over the wire' (aka a network).
https://github.com/llvm/llvm-project/pull/216499
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
