.dynsym and .dynstr are allocatable and therefore normally are placed
before non-allocatable .strtab, .shstrtab, .symtab sections.
But we are placing them after currently what creates a mix of
alloc/non-alloc sections and does not look normal.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
There is a typo in the title. I think you meant Change the order of implicitly created sections.
(I think default can be removed.)
llvm/test/tools/yaml2obj/ELF/implicit-sections-info.yaml | ||
---|---|---|
58 | Indent, i.e. CASE2-SAME: 1 |
llvm/test/tools/yaml2obj/ELF/implicit-sections-info.yaml | ||
---|---|---|
58 | I know I suggested this behaviour previously, but I realise that there is a slight flaw in it, as it will also match "Info: 1234" or "Info: 2211" for example. I think you need ^$ regex markers too. |
- Addressed review comments.
llvm/test/tools/yaml2obj/ELF/implicit-sections-info.yaml | ||
---|---|---|
58 | I am not sure how to use {{^}} with -SAME # CASE1: Info: # CASE1-SAME: {{^}}2{{$}} I think we can use -NOT, I did it here. Looks fine? |
llvm/test/tools/yaml2obj/ELF/implicit-sections-info.yaml | ||
---|---|---|
58 | Looks fine to me. I think you need a space after the ^ pattern with CHECK-SAME, though I'm not certain: CASE1-SAME: {{^}} 2{{$}}. My understanding is that the ^ character matches the start of a line, and also the end of the previous match, because of the way FileCheck's system is set up. Whitespace will be significant (but canoncalized to a single space). |
llvm/test/tools/yaml2obj/ELF/implicit-sections-info.yaml | ||
---|---|---|
58 | {{^}} 2{{$}} works! As well as {{^}} 2{{$}} Thanks! |
Indent, i.e. CASE2-SAME: 1