llvm: add full LTO bitcode writer#40
Merged
Merged
Conversation
zhouguangyuan0718
changed the title
zhouguangyuan0718
force-pushed
the
codex/support-llgo-lto
branch
from
a1274e6 to
92cb6b8
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
WriteFullLTOBitcodeToMemoryBufferand the LLVM C++ shim used to emit full LTO bitcodeThinLTO = 0when missingWhy
llgo LTO support needs a full LTO bitcode path alongside the existing ThinLTO writer. This adds the go-llvm API surface and LLVM backport glue needed by llgo to produce full LTO-compatible bitcode.
Validation
go test ./...