From: Petr Ovtchenkov <ptr@void-ptr.info>
To: Nick Clifton <nickc@redhat.com>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>, binutils@sourceware.org
Subject: Re: [RFC] ld: Add random filling for unspecified section contents
Date: Tue, 16 May 2017 07:24:00 -0000 [thread overview]
Message-ID: <20170516102411.191a1d1a@void-ptr.info> (raw)
In-Reply-To: <8dba78f6-c0ba-918f-3ae9-94092e787433@redhat.com>
Good day,
On Mon, 15 May 2017 17:43:00 +0100
Nick Clifton <nickc@redhat.com> wrote:
>
> > Do you consider pros/contras for "Add random filling for unspecified section contents",
> > in particular with relation to "Reproducible Builds" issue?
>
> Part of the proposal did include a new linker command line option to set
> the seed for random number generation, so that reproducible, random
> contents would be generated.
Reproducible pseudo-random filling? Hmm, is any sense in this?
WBR,
--
- Petr
next prev parent reply other threads:[~2017-05-16 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 22:40 Andrew Burgess
2017-04-20 13:43 ` Nick Clifton
2017-04-26 9:26 ` Andrew Burgess
2017-05-05 9:39 ` Nick Clifton
2017-05-09 16:36 ` Andrew Burgess
2017-05-15 15:58 ` Petr Ovtchenkov
2017-05-15 16:43 ` Nick Clifton
2017-05-16 7:24 ` Petr Ovtchenkov [this message]
2017-05-17 15:48 ` Andrew Burgess
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=20170516102411.191a1d1a@void-ptr.info \
--to=ptr@void-ptr.info \
--cc=andrew.burgess@embecosm.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).