danog/gllvm
1
0
Fork 0
mirror of https://github.com/danog/gllvm.git synced 2024-11-30 04:09:02 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
Missing yada yada for the LTO_LINKING_FLAGS.
This commit is contained in:
Ian A Mason 2021-02-18 10:29:02 -08:00 committed by GitHub
parent 70a9d23b20
commit 5979228b2e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -248,7 +248,11 @@ flags, for example `"-flto -fwhole-program-vtables"`.
If the package you are building happens to take advantage of recent `clang` developments If the package you are building happens to take advantage of recent `clang` developments
such as *link time optimization* (indicated by the presence of compiler flag `-flto`), then such as *link time optimization* (indicated by the presence of compiler flag `-flto`), then
your build is unlikely to produce anything that `get-bc` will work on. This is to be your build is unlikely to produce anything that `get-bc` will work on. This is to be
expected. expected. When working under these flags, the compiler actually produces object files that are bitcode,
your only recourse here is to try and save these object files, and retrieve them yourself.
This can be done by setting the `LTO_LINKING_FLAGS` to be something like
`"-g -Wl,-plugin-opt=save-temps"` which will be appended to the flags at link time.
This will at least preserve the bitcode files, even if `get-bc` will not be able to retrieve them for you.
## Developer tools ## Developer tools