Lld test ELF/linkerscript/thunk-gen-mips.s was accidentally disabled due
to the use of wrong FileCheck directives. As a result the test seems to
have bitrotted as it fails to pass if fixing the directive. To ease
updates to the test in case of change of the start address the checks
have been changed to use numeric variables to express all the addresses
based on the start address.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lld/test/ELF/linkerscript/thunk-gen-mips.s | ||
---|---|---|
18 | What does [[#%x, START_ADDR:<0x100000]] mean? s/was/were/ I think |
LGTM
Initially the test case just checks that LLD does not crash under some conditions. It's not mandatory to test exact symbols' values and/or offsets between symbols. But after this fix the test additionally becomes more tolerant to exact symbol addresses. It's fine.
As to me, I'd remove the "Ideally we'd use..." comment.
lld/test/ELF/linkerscript/thunk-gen-mips.s | ||
---|---|---|
18 | It is not supported by FileCheck yet but the syntax for numeric expression was designed to allow for it. The meaning would be: Match an lower case hex number (%x) that is less in value than 0x100000 and assign its value to START_ADDR. But reading the testcase again it is clear the address of start does not matter but only the offset of the 2 other symbols relative to it. Therefore I'm going to remove the 0x30 and just set START_ADDR to whatever is the address of start unconditionally. |
What does [[#%x, START_ADDR:<0x100000]] mean?
s/was/were/ I think