wasm-linker: generate 'producers' section #13054
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `producers` section contains meta data of the binary and/or object file. It *can* contain the source language, the tool it was processed by, and/or the SDK that was used to produce the file. For now, we always set the language and processed-by fields to Zig. In the future we will parse linked object files to detect their producers sections and append (if different) their language, SDK and processed-by fields.
This also turns off non-debug modes for the bss linker tests for Wasm. This is done as it's not required to guarantee to zero out the bss section for non-debug modes.
Luukdegram
force-pushed
the
wasm-producer
branch
from
861fafb
to
fda75f5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implements the
producerscustom section. This section contains meta data describing what tools were used to generate the binary as well as what the source language was. Other tools can use this information to apply certain transformations (such as name mangling for c++), or even optimizations.For now, we always emit Zig as source language and as tool used to produce the binary. The next step would be to parse all linked object files and static archives and append their source languages and tools + SDK's also.