[NFCI][StaticDataLayout] Introduce an LLVM option to control the emission of .hot
data section prefix.
#158172
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
-preserve-hot-data-section-prefix
, which allows for disabling the.hot
prefix for data sections in the intermediate object files (i.e., linker input files). The option defaults to true to maintain existing behavior.Context:
-keep-data-section-prefix
to map input sections to output sections based on hotness. When the option is enabled and linker input files have three kinds of rodata sections (.rodata
,.rodata.hot
,.rodata.unlikely
), the executable will also have three kinds of sections. OTOH, to have simpler executable and more important to avoid unstudied performance penalty from segregated hot and lukewarm data , we'd prefer to have an.rodata.unlikely
to group the cold data, and keep the rest (hot or lukewarm) in.rodata
section.