yekuang
yekuang
Cool! Can we include this to https://github.com/taichi-dev/taichi/tree/master/docs ?
Notes: a few things we should highlight: * [ ] Use `clang` to build Taichi on Linux (maybe all?) platforms * [ ] Give out specific instruction like `TAICHI_CMAKE_ARGS="..." python...
FYI: https://github.com/taichi-dev/taichi/issues/2190 and https://github.com/taichi-dev/taichi/issues/4944
Is there a middle ground we can find out? E.g. how easy is it for us to migrate the implementation from caching LLVM to caching CHI IR? If most users...
> I wonder if it would be better to allow the users to issue queries via unified interfaces like ti_{get|set}_texture_property with a string or enum property name? From the RHI...
Thanks, I also find it useful to have a per-kernel config. I favor the third option, because that's 1) the least intrusive change, and 2) aligned with `loop_config`. ```py @ti.kernel_config(print_ir=True,...
Cool! Could you also provide a dependency graph. https://excalidraw.com/ could be your friend (@ailzhang recommended)
Nice graph! IIUC, `type` and `snode` are sub-components under `ir`? Also `artifact` is probably too generic, better come up with a better naming for it... (Context: this refers to the...
Would be great to separate out the unified device API! I'd call it `rhi` , though. @bobcao3
Note that right now also everything is grouped in a two-level namespace: `::taichi::lang`. We should also consider just using `taichi`, and only the components that are truly language-related goes to...