(might be easier to pick up from the thread where this came up or at least
CC/to the folks you're referring to (though perhaps you did and that got
stripped by the mailing list or something, not sure) - at least for me, I
have highlights for emails addressed to me that helps prioritizing/knowing
if there's a response expected from me & handy for context - I forget what
particular thing we were talking about regard to LTO & would have to go
search up the original thread for the context)
Yeah, I don't know too much about the LLVM release process, to be honest,
it surprises me that libLLVMgold.so is no longer part of the release.
But you should be able to use LTO with lld instead: -flto -fuse-ld=lld
Give that a go? Happy to help further.
On Tue, Feb 22, 2022 at 10:41 AM David Anderson via Dwarf-Discuss <
dwarf-discuss@lists.dwarfstd.org> wrote:
> A followon To Jan K and David B Feb 1 2022:
>
> Binary release on github
> clang+llvm-13.0.0-x86_64-linux-gnu-ubuntu-20.04.tar.xz
> does not contain LLVMgold.so
>
> So adding -flto just results in the inability
> compile anything.
>
> Suggestions?
> Thanks.
> David Anderson
>
> --
> Overflow on /dev/null, please empty the bit bucket.
> -- seen on slashdot.org
> ___
> Dwarf-Discuss mailing list
> Dwarf-Discuss@lists.dwarfstd.org
> http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
>
___
Dwarf-Discuss mailing list
Dwarf-Discuss@lists.dwarfstd.org
http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org
