From: Dave Jones <davej@redhat.com>
To: Ildar Muslukhov <ildarm@google.com>
Cc: trinity@vger.kernel.org
Subject: Re: Reproducible run and binary logs (ideas)
Date: Thu, 19 Sep 2013 11:07:47 -0400 [thread overview]
Message-ID: <20130919150746.GA2416@redhat.com> (raw)
In-Reply-To: <CAEGbLtsg8_xLx9YvdrZ-gLWR4UqSQ+DT4mzEV9BfGnf-uHxDjQ@mail.gmail.com>
On Wed, Sep 18, 2013 at 12:48:40PM -0700, Ildar Muslukhov wrote:
> Although, the way it is implemented right now is a bit risky, since
> the rand functions are called in place, and we cannot guarantee that
> no other code (like gcc libraries) hasn't made a call to rand()
> function, thus moving the rand queue forward.
This whole idea seems to hang on this statement, and it bothers me.
Can this even happen ? I'm not sure it can.
And even if it can, surely it's going to happen again when we re-run
with the same seed, so we don't need to compensate for it.
Before going too far down this rabbit hole, I want to be sure we're not
over-engineering for a problem that actually isn't.
Dave
next prev parent reply other threads:[~2013-09-19 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 19:48 Reproducible run and binary logs (ideas) Ildar Muslukhov
2013-09-19 15:07 ` Dave Jones [this message]
2013-09-19 16:03 ` Ildar Muslukhov
2013-09-19 16:21 ` Dave Jones
2013-09-19 16:49 ` Vince Weaver
2013-09-19 17:04 ` Ildar Muslukhov
2013-09-19 17:15 ` Ildar Muslukhov
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=20130919150746.GA2416@redhat.com \
--to=davej@redhat.com \
--cc=ildarm@google.com \
--cc=trinity@vger.kernel.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.