From: Stephan Gatzka <stephan@gatzka.org>
To: gcc-help@gcc.gnu.org
Subject: reproducible build
Date: Sun, 23 Aug 2015 13:50:00 -0000 [thread overview]
Message-ID: <1440337839.2033.4.camel@gatzka.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
Hi!
I just added support for reproducible builds (-frandom-seed=) into the
qbs build system.
For a automated test case I'd like to have a small snippet of C/C++
code, which definitely leads to different object files if compiled
twice.
I wasn't able to write such a snippet, so any help would be very
appreciated.
Regards,
Stephan
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3678 bytes --]
next reply other threads:[~2015-08-23 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 13:50 Stephan Gatzka [this message]
2015-08-23 21:10 ` Martin Sebor
2015-08-24 4:46 ` Stephan Gatzka
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=1440337839.2033.4.camel@gatzka.org \
--to=stephan@gatzka.org \
--cc=gcc-help@gcc.gnu.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 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).