This adds support for the non-location, non-elements, non-affine
builtin attributes.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Nice!
mlir/docs/BytecodeFormat.md | ||
---|---|---|
78 | zigzag encoding for 64-bits integers: | |
mlir/include/mlir/Bytecode/BytecodeImplementation.h | ||
175–176 | What about this TODO? | |
181 | Worth mentioning that this is using ZigZag encoding for symmetry between negative and positive numbers. Right, now if I have a uintX_t, it's not clear to me why one would pick this method instead of the one above directly for example. | |
mlir/lib/Bytecode/Reader/BytecodeReader.cpp | ||
137 | This bit manipulation is magic :) (Translation: I'm too lazy to try to figure it out right now, but hey if it works...) |
mlir/include/mlir/Bytecode/BytecodeImplementation.h | ||
---|---|---|
175–176 | Yeah, I was deferring it until I had a method that needed it, but let me just add now (it just forwards to the underlying method anyways). | |
mlir/lib/Bytecode/Reader/BytecodeReader.cpp | ||
137 | I added a comment of the actual formula, which is easier to read IMO. This right here though, is the same thing that protobufs use for zigzag decoding. |
Nice, reads without surprises :-)
mlir/lib/Bytecode/Reader/BytecodeReader.cpp | ||
---|---|---|
563 | I would have thought read<What><How> would result in better method sorting order. E.g., if I want to read an APLfloat , autocomplete would give me the variants just by me saying readAPFloat ( | |
mlir/lib/IR/BuiltinDialectBytecode.cpp | ||
83 | Should we add comment why we don't have or want DenseElementsAttr here? | |
300–301 | Keep these in alphabetical order? |
mlir/lib/IR/BuiltinDialectBytecode.cpp | ||
---|---|---|
83 | I'm leaving that out for now, because I just haven't gotten to all of the attributes (so I haven't had time to figure out what we want to do there). We'll need to have a conversation on some of the attributes though, to figure out if we are planning on deleting things. We could also just add support for now, but then just delete it whenever we do drop the attributes. This all factors into versioning a bit as well (I don't want to version until we figure out what we want to change and how). |
zigzag encoding for 64-bits integers: