From 831eb6640aea7d076c5dd752dd5ecdf245a78c7a Mon Sep 17 00:00:00 2001 From: Matthias Gehre Date: Wed, 6 Nov 2024 17:14:33 +0100 Subject: [PATCH] emitc.include: don't require the parent to be a ModuleOp `#include` make sense everywhere, and in particular we need to allow them inside a `emitc.tu`. But sometimes we might even want to have an `#include` in a function body. --- mlir/include/mlir/Dialect/EmitC/IR/EmitC.td | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mlir/include/mlir/Dialect/EmitC/IR/EmitC.td b/mlir/include/mlir/Dialect/EmitC/IR/EmitC.td index 78c420997dac655..3f290f68b85dc80 100644 --- a/mlir/include/mlir/Dialect/EmitC/IR/EmitC.td +++ b/mlir/include/mlir/Dialect/EmitC/IR/EmitC.td @@ -774,7 +774,7 @@ def EmitC_ReturnOp : EmitC_Op<"return", [Pure, HasParent<"FuncOp">, } def EmitC_IncludeOp - : EmitC_Op<"include", [HasParent<"ModuleOp">]> { + : EmitC_Op<"include", []> { let summary = "Include operation"; let description = [{ The `emitc.include` operation allows to define a source file inclusion via the