All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sundeep KOKKONDA" <sundeep.kokkonda@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Rust reproducibility issue summary
Date: Sun, 07 Jul 2024 00:12:35 -0700	[thread overview]
Message-ID: <20061.1720336355685054373@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_fJbN94ty+Y6n78Tmgh8-35Wk8TuuqruVVtszrx1Mk-A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

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.

[-- Attachment #2: Type: text/html, Size: 3657 bytes --]

      reply	other threads:[~2024-07-07  7:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 13:28 Rust reproducibility issue summary Richard Purdie
2024-05-31 13:33 ` Patchtest results for " patchtest
2024-06-01 10:27 ` [OE-core] " Alexander Kanavin
2024-06-03  4:23   ` Sundeep KOKKONDA
2024-06-03  7:08     ` Sundeep KOKKONDA
2024-06-03  9:54       ` Alexander Kanavin
2024-06-24  3:59         ` Sundeep KOKKONDA
2024-06-24  8:20           ` [OE-core] " Alexander Kanavin
2024-06-24  9:07             ` Sundeep KOKKONDA
2024-06-24  9:11               ` [OE-core] " Alexander Kanavin
     [not found]                 ` <12dd26bc-91c1-4af7-b756-ff42967fe5f6@windriver.com>
     [not found]                   ` <CANNYZj-jWdnRXTbFL0fMYvbVTAeSBi3qka9WgcixrMPsf7Tmww@mail.gmail.com>
2024-07-03  8:09                     ` Sundeep KOKKONDA
2024-07-03  9:58                       ` Alexander Kanavin
2024-07-04 15:13                         ` Sundeep KOKKONDA
2024-07-04 15:21                           ` [OE-core] " Alexander Kanavin
2024-07-04 16:47                             ` Randy MacLeod
2024-07-05 11:36                               ` Alexander Kanavin
2024-07-07  6:24                                 ` Sundeep KOKKONDA
     [not found]               ` <17DBE5C236FF6606.28936@lists.openembedded.org>
2024-06-24 12:22                 ` [OE-core] " Alexander Kanavin
2024-06-25  3:02                   ` Sundeep KOKKONDA
2024-06-25  9:06                     ` Alexander Kanavin
2024-07-05 15:25       ` Alexander Kanavin
2024-07-07  7:12         ` Sundeep KOKKONDA [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061.1720336355685054373@lists.openembedded.org \
    --to=sundeep.kokkonda@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.