This is quite minimal so far, introduce them with .section,
fill them with .int8 or .asciz, end with .size
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Note to reviewers: this is a pretty minimal set of directives so far, if you have any opinions which others are vital to add in this patch, let me know :)
Comment Actions
Great!
lib/MC/MCParser/WasmAsmParser.cpp | ||
---|---|---|
139 ↗ | (On Diff #188285) | How about .data ? |
lib/Target/WebAssembly/AsmParser/WebAssemblyAsmParser.cpp | ||
656 ↗ | (On Diff #188285) | What will happen now if we hit this case? Should we assert/unreachable? |
test/MC/WebAssembly/basic-assembly.s | ||
87 ↗ | (On Diff #188285) | Indentation inconsistent with above |
173 ↗ | (On Diff #188285) | To these end up as two different fragments with in the data section? Just curious how this is preserved through mc. |
test/MC/WebAssembly/data-section.s | ||
2 ↗ | (On Diff #188285) | Command is wrong. We do check! |
11 ↗ | (On Diff #188285) | Consistent indention with directives below? |
lib/Target/WebAssembly/AsmParser/WebAssemblyAsmParser.cpp | ||
---|---|---|
656 ↗ | (On Diff #188285) | Forgot I needed to fill that in. Now errors if not in a data section. |
test/MC/WebAssembly/basic-assembly.s | ||
173 ↗ | (On Diff #188285) | I'm not entirely sure, as I am still foggy on how fragments work. It does end up adjacent in the binary, which is what matters? |