Niansong Zhang

Hi @erick-xanadu, with a working `cudaq` version I was able to further test my implementation, and I discovered some issues that I'd like to discuss. The issue is that a...

To compile any MLIR IR with gcc/clang, we can do this: ```sh mlir-opt example.mlir \ --convert-linalg-to-affine-loops \ --one-shot-bufferize \ --lower-affine \ --convert-scf-to-cf \ --convert-cf-to-llvm \ --convert-func-to-llvm \ --convert-arith-to-llvm \ --finalize-memref-to-llvm...

Associated allo program to this sample: ```python import allo from allo.ir.types import int32, float32 import numpy as np def test_library_higher_dimension_ops(enable_tensor): M = 5 N = 4 K = 3 L...

Hi Sofia, could you add the HeteroCL code piece as well?

Removed tutorial tag as this is not part of the tutorial

Yes it's related to #133 , general expr to initialize scalar with struct type is WIP

Segmentation fault is caused by an `unrealized_conversion_cast` operation from `i8` to `!hcl.struct`. 1. We should support initializing struct with general expression. However, I think we should restrict the bitwidth of...

@jcasas00 What is the expected behavior when we cast `i8` to `!hcl.struct`? Should we split `i8` to `i4` `i4` first and extend them to `i8` or extend `i8` to `i16`...

This issue should be fixed by ddcb3d42ba4e3dcb0153245d55ba86b2913c1981. I agree that the cast should be explicit. The current integer to struct checks two things: - The integer bitwidth is the same...

I agree, I think we should support nested structs. What I meant by "no automatic bitcast" is that we don't do integer slice -> float/fixed bitcast.