From 5abaf5dce692fae53830ba2b56e1167dd3cc16bd Mon Sep 17 00:00:00 2001 From: Jeremy Bradley-Silverio Donato Date: Thu, 6 Jan 2022 17:37:18 +0100 Subject: [PATCH] docs: Update mlir.md --- docs/dev/explanation/mlir.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dev/explanation/mlir.md b/docs/dev/explanation/mlir.md index 914695599..507f4eb20 100644 --- a/docs/dev/explanation/mlir.md +++ b/docs/dev/explanation/mlir.md @@ -17,7 +17,7 @@ The conversion uses as input the operation graph to convert, as well as a dictio ## Define function signature -The first step would be to define the function signature (excluding return value at this point). We will convert input node's types to MLIR (e.g. convert `EncryptedTensor(Integer(64, is_signed=False), shape=(4,))` to `tensor<4xi64>`) and map their values to the argument of the function. So if we had an operation graph with one `EncryptedScalar(Integer(7, is_signed=False))`, we will get an MLIR function like `func @main(%arg0 : !FHE.eint<7>) -> ()`. Note that the return type would be detected automatically later on when returning MLIR values. +The first step is to define the function signature (excluding return value at this point). We will convert the input node's types to MLIR (e.g. convert `EncryptedTensor(Integer(64, is_signed=False), shape=(4,))` to `tensor<4xi64>`) and map their values to the argument of the function. So if we had an operation graph with one `EncryptedScalar(Integer(7, is_signed=False))`, we will get an MLIR function like `func @main(%arg0 : !FHE.eint<7>) -> ()`. Note that the return type would be detected automatically later on when returning MLIR values. ## Convert nodes in the OpGraph