- match sections to one or more headers
- use NONE header to discard layouting of specific section
- support all available header types (except custom numeric values)
- TLS section layout doesn't work yet
- test cases are provided
Details
Diff Detail
Event Timeline
First round of review.
ELF/LinkerScript.cpp | ||
---|---|---|
295–298 | StringRef Name = next(); uint32_t Type = readPhdrType(); Config->Phdrs.emplace_back({Name, Type}); | |
329 | It's better to be a bit more specific, say, read zero or more tokens in the form of :phdr. | |
330 | for (;;) for consistency. | |
ELF/Writer.cpp | ||
971 | This function is already too long and need to be refactored. Please at least factor this new code out from this function. |
Updated:
- style fixes in linker script's PHDRS parsing
- move custom header processing out to a separate method
Updated:
- Add method comment
- Simplify custom header layout loop
- Check if no sections assigned to custom headers
- Improve NONE header handling
- Style fixes in the header layout loop
ELF/Writer.cpp | ||
---|---|---|
864 | Done, thanks. This also allowed me to add one more check with test case when no sections assigned to PHDRS. |
ELF/Writer.cpp | ||
---|---|---|
873 | I wanted to split this into multiple functions -- this function is 90 lines long which feels too long to me. |
Updated:
- move out some functionality to couple of methods
- improve NONE header handling (it now can be specified with other headers and just ignored)
I'm sorry that this code review was slipped from my inbox.
ELF/Writer.cpp | ||
---|---|---|
43 | Please use std::vector if there's no strong reason to use SmallVector. | |
96–97 | These fields need a brief comment that they are for the linker script's phdr command. | |
864 | Please add a function comment. | |
868 | Instead of const std::vector<X> &, you want to use ArrayRef<X>. | |
871–901 | This also needs a function comment. | |
903–925 | This needs a comment too. They are all non-trivial, so they need some descriptions to help reader understand what they are supposed to do. |
Updated:
- Use std::vector instead of SmallVector
- Add comments to methods
- Rename fillPhdrs -> fillUnusedPhdrs
ELF/Writer.cpp | ||
---|---|---|
868 | I can't do that because lookup returns temporary object, and I bind it to const reference to prolong its lifetime to the end of the scope. ArrayRef constructs without copying the vector, so it'll be destroyed before used. |
ELF/Writer.cpp | ||
---|---|---|
54 | Since IndicesVector is now just a std::vector, I'd write std::vector<size_t> instead of IndicesVector. | |
98 | Ditto | |
879 | Please do not use auto here as the actual type is not obvious in this local context. | |
883–884 | PhdrInds.insert(PhdrIns.end(), std::begin(It->second), std::end(It->second)) is more common? | |
927–936 | Can you please write more details about how you process PHDR command for those who happens to come to this file and read this code (not for me who is reading only the delta), so that they can get the whole picture what you are doing with this function (and the helper functions you added above) without reading all the code? |
Updated:
- Remove IndicesVector typedef
- Replace std::copy with insert into vector
- Add more comments to functions
ELF/Writer.cpp | ||
---|---|---|
879 | I thought we agreed to use auto for cases when returning iterators from methods like find and similar, no? |
ELF/Writer.cpp | ||
---|---|---|
1052 | Wouldn`t it be better to write something like: if (hasCustomPhdrs()) { layoutCustomPhdrs(VA, FileOff); return; } And just copy a piece of left logic from below to layoutCustomPhdrs() or even to separate it to another method ? Also in currect variant bracket is missed: if (hasCustomPhdrs()) { | |
1056 | Change is not relative to this patch (fix of formatting). | |
1206 | There should be brackets I think: for (const std::pair<StringRef, OutputSectionDescription> &OutSec : Config->OutputSections) { ... |
ELF/Writer.cpp | ||
---|---|---|
1052 | No, it's not better, because there already were cases when the common logic below was extended. This would have caused logical issue in the case you propose. Concerning the braces - I don't remember us putting them for one-line operator blocks. | |
1056 | It's related, because you don't see that the whole code moved by one tab left (by default, ignore space mode is on). So this is the result of clang-formatting the whole shifted piece. | |
1206 | No, I was told to remove these earlier. We don't use braces for blocks that constitute of one operator. |
ELF/Writer.cpp | ||
---|---|---|
1052 | (About braces): I found multiple usings for one-line blocks: | |
1056 | Yep, I know its moved, I just supposed correct way would be to not format that part here (to format it in separate patch). | |
1206 | Hmm that wierd for me then :) Because quick search shows that sometimes we do: Writer<ELFT>::copyLocalSymbols(); |
I'm sorry for the delay. I was thinking if this is a right design. Will send code review comments soon.
I don't like the current code to create a program header because it's not easy to read, and this is yet another piece of code that also creates a program header. This also feels a bit too complicated. I think one reason why phdr creation is hard to read is because the functions doing that are members of Writer, and they mutate Writer's fields.
They also do too much stuff once. They are creating program header while assigning addresses to sections.
Abstractly, in order to support PHDRS command, we want to have a class or a function that create a list of program header fields, and associate OutputSections to zero or more program header field. Can you model that way?