Previously these directives were always interpreted as having an extra
blank line after them.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Previously these directives were always interpreted as having an extra blank line after them.
EndOfStatement was not consumed and the next AsmParser::parseStatement would consume EndOfStatement and add a blank line.
| llvm/test/MC/AsmParser/directive-parse-err.s | ||
|---|---|---|
| 1 | Please merge this into a .cfi_* parsing test. You can leverage -defsym ERR=1 to check errors. See MC/ELF/reloc-directive.s for an example | |
| 6 | [[@LINE+1]] is deprecated. Use [[#@LINE+1]] | |
| llvm/test/MC/AsmParser/round-trip.s | ||
| 16 | One pair .cfi_startproc of should be sufficient. | |
| llvm/test/MC/AsmParser/directive-parse-err.s | ||
|---|---|---|
| 1 | To clarify, is there an "omnibus" cfi parsing test under MC/AsmParser? I see a few specific examples, but not just cfi.s. Did you have a particular test in mind? | |
| 6 | Sorry, I keep forgetting this when I look at existing tests as templates. I'll update this in the next patch! | |
| llvm/test/MC/AsmParser/round-trip.s | ||
| 16 | Agreed, I'm not sure why I added the repeated pairs, I'll update this in the next patch. | |
| llvm/test/MC/AsmParser/directive-parse-err.s | ||
|---|---|---|
| 1 | They don't have to be under MC/AsmParser. You may use MC/ELF where there are a few cfi*.s | |
Merge new test into existing cfi.s test, remove gratuitous directives in the
round trip test. Replace use of deprecated FileCheck syntax.
| llvm/test/MC/AsmParser/directive-parse-err.s | ||
|---|---|---|
| 1 | Ok, it just seemed like tests under ELF/ were for the binary result, not necessarily for the behavior of the parser directly. | |
Thanks!
| llvm/test/MC/ELF/cfi.s | ||
|---|---|---|
| 439 ↗ | (On Diff #309601) | I think it is more common to place RUN lines above all the CHECK lines. MC/ELF does have some parser tests (-filetype=asm). I agree that the organization of tests is a bit unclear but I think MC/ELF for these .cfi_* is fine because they are indeed specific to certain binary formats. |
Please merge this into a .cfi_* parsing test. You can leverage -defsym ERR=1 to check errors. See MC/ELF/reloc-directive.s for an example