diff options
author | Nikita Popov <npopov@redhat.com> | 2024-01-19 14:55:31 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-01-19 14:55:31 +0100 |
commit | 6f371149c1c9f24bede8a799b7c2c9562740aa62 (patch) | |
tree | d108c7694874c321e3b2dfce03a110083a9f6df0 /llvm/lib/FileCheck/FileCheck.cpp | |
parent | ea9d75aa2ad64330ffc030b7ce0fcc16b55cf3bb (diff) | |
download | llvm-6f371149c1c9f24bede8a799b7c2c9562740aa62.zip llvm-6f371149c1c9f24bede8a799b7c2c9562740aa62.tar.gz llvm-6f371149c1c9f24bede8a799b7c2c9562740aa62.tar.bz2 |
[AsmParser] Don't require value numbers to be consecutive (#78171)
Currently, the IR parser requires that %n style numbered values are
consecutive. This means that the IR becomes invalid as soon as you
remove an instruction, argument or block. This makes it very annoying to
modify IR without running it through instnamer first.
I don't think there is any good reason to impose this requirement. This
PR relaxes it to allow value IDs to be non-consecutive, but it still
keeps the requirement that they're increasing (i.e. you can't skip a
value number and then assign it later).
This only implements support for skipping numbers for local values. We
should extend this to global values in the future as well.
Diffstat (limited to 'llvm/lib/FileCheck/FileCheck.cpp')
0 files changed, 0 insertions, 0 deletions