Otherwise subsequent .option arch, +foo directives (but not -, since
those have their own separate validation) fail the parseFeatureBits
check, leading to cascading errors.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/test/MC/RISCV/option-invalid.s | ||
---|---|---|
50 |
llvm/test/MC/RISCV/option-invalid.s | ||
---|---|---|
50 | Short comments don't normally get full stops? |
llvm/test/MC/RISCV/option-invalid.s | ||
---|---|---|
50 | In comments, a complete sentence gets a full stop. An incomplete one doesn't. ( |
llvm/test/MC/RISCV/option-invalid.s | ||
---|---|---|
50 | Like many comments I view this more as a sentence fragment that happens to technically be a complete sentence. Adding a full stop changes the tone of the comment in a way that isn't appropriate IMO. I'm not fundamentally opposed to it, it just feels quite unnatural to do. |
llvm/test/MC/RISCV/option-invalid.s | ||
---|---|---|
50 | OK, I don't actually mind much about the comment style in the tests. It was just a suggestion. Feel free to land the patch as is:) |