search for: cederstrand

...ccache can just use the checksum of /usr/bin/clang to verify that it can use the cache. Would it be possible to unify the above output as to create deterministic builds of clang, clang++ and tblgen? I believe the binaries are created with binutils-as and binutils-ld, if it matters. Thanks, Erik Cederstrand -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1928 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101112/7378e939/attachment.bin>

On 12.11.2010 15:26, Erik Cederstrand wrote: > I have noticed that two consecutive builds of clang, clang++ and tblgen don't produce identical binaries (as in md5 sums) on identical source code (I'm on FreeBSD). I ran strings(1) on the two clang binaries, and I get the following: > 251862c251862 > < N4llvm3sys11Thr...

On Nov 12, 2010, at 7:10 AM, Sebastian Redl wrote: > On 12.11.2010 15:26, Erik Cederstrand wrote: >> I have noticed that two consecutive builds of clang, clang++ and tblgen don't produce identical binaries (as in md5 sums) on identical source code (I'm on FreeBSD). I ran strings(1) on the two clang binaries, and I get the following: >> 251862c251862 >> < N4l...

Yes, this is controlled by the -frandom-seed flag. Sadly, it is expected behavior. -Chris On Nov 12, 2010, at 7:10 AM, Sebastian Redl <sebastian.redl at getdesigned.at> wrote: > On 12.11.2010 15:26, Erik Cederstrand wrote: >> I have noticed that two consecutive builds of clang, clang++ and tblgen don't produce identical binaries (as in md5 sums) on identical source code (I'm on FreeBSD). I ran strings(1) on the two clang binaries, and I get the following: >> 251862c251862 >> < N4l...

...Nov 12, 2010, at 9:19 AM, Chris Lattner wrote: > Yes, this is controlled by the -frandom-seed flag. Sadly, it is expected behavior. > > -Chris > > On Nov 12, 2010, at 7:10 AM, Sebastian Redl <sebastian.redl at getdesigned.at> wrote: > >> On 12.11.2010 15:26, Erik Cederstrand wrote: >>> I have noticed that two consecutive builds of clang, clang++ and tblgen don't produce identical binaries (as in md5 sums) on identical source code (I'm on FreeBSD). I ran strings(1) on the two clang binaries, and I get the following: >>> 251862c251862 >>&g...

Den 12/11/2010 kl. 18.48 skrev Chris Lattner: > Oh, I should point out that using randomness is the unfortunate part, but you can get deterministic builds by passing -frandom-seed=0 to clang and/or gcc. I'll try that. I assume that the randomness has a purpose, so what are the negative implications of setting -frandom-seed=0? Will i still have a functioning compiler? :-) Thanks, Erik