Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/docs/Bindings/Python.md | ||
---|---|---|
1128–1130 | The extra files under python/mlir/dialects where added specifically to include Attributes.td. Can we remove them entirely now that we don't need the other include? |
mlir/docs/Bindings/Python.md | ||
---|---|---|
1128–1130 | I had tried that initially, but the declare_mlir_dialect_python_bindings cmake function uses the .td file path to determine where to place the generated python file: I could make relative_td_directory there an argument to declare_mlir_dialect_python_bindings though, let me try that. | |
1132–1138 | Any particular reason the table-generated python file shouldn't be called <dialect-namespace>.py? While I'm at it I could try to get rid of the ones that are just from ._dialect_ops_gen import *. |
LGTM. Cmake changes and file deletion can come in a separate patch. Please ping be on discord or some other chat channel if you need me to take another look at this.
mlir/docs/Bindings/Python.md | ||
---|---|---|
1128–1130 | I see. No need to block this patch on cmake changes, those can come later as long as this patch has a TODO. Thanks! | |
1132–1138 | Many dialect packages have more initialization than just importing the generated bindings. Furthermore, the mixin mechanism relies on the files being named _dialect_ops_gen and _dialect_ops_ext, respectively. I'd rather keep this as is and not introduce extra complexity in the build system (choosing whether to generate an _ops_gen file or directly a dialect files) to spare a dozen lines of boilerplate. |
The extra files under python/mlir/dialects where added specifically to include Attributes.td. Can we remove them entirely now that we don't need the other include?