On Fri, Jul 5, 2024 at 08:55 PM, Alexander Kanavin wrote:

> 
> After reading the issue and poking at the rustdoc binaries on my local
> disk, I think the key is in finding where those llvm.<hash> suffixes are
> generated and *how*. Something (presumably rust-llvm) puts them there, so
> narrowing down to the point where that non-reproducible value is decided
> would help a lot in finding out why it sometimes changes. It does require
> navigating and reading a mountain of unfamiliar llvm code, this is what
> makes the issue difficult.

The.llvm.<hash> are generated by ThinLTO optimizations, and this is enabled by 
default. I tried a build by disabling this optimization but that doesn't solved 
the problem. By disabling lto, the.llvm.<hash> are not seen in rustdoc binary 
but still the binaries are differed. I'll have to check with llvm community 
that how this hash depends/affects based on build-dir name/length.

Thanks,
Sundeep K.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#201617): 
https://lists.openembedded.org/g/openembedded-core/message/201617
Mute This Topic: https://lists.openembedded.org/mt/106407787/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to