Re: gcc-4.9.1 generating different code between two successive builds

I will investigate next week, and have a look at whether ASLR is turned off in our build system. But if it was on, I would expect more than a single .o file to be different. At this point in time, by disabling libcilkrts, and one other option, I can't remember which right now, I can get gcc buildi

Re: gcc-4.9.1 generating different code between two successive builds

On 30/12/15 15:33, Georg-Johann Lay wrote: > Some parts of the compiler use the address of objects to compute > hashes, but I don't remember which part(s) actually do this. That > technique can lead to different code for different runs of the > compiler even on the same system. This is hard to r

Re: gcc-4.9.1 generating different code between two successive builds

Cole schrieb: Hi, I am busy trying to generate a package for gcc that is consistent between two successive builds, and I am now down to the final few files. I am stuck with the file: cilk-abi-cilk-for.o, which is obviously built with -O2, but between two successive builds, the assembly code gen

Re: gcc-4.9.1 generating different code between two successive builds

On 12/21/2015 11:30 PM, Cole wrote: HI Martin, Thanks very much for the suggestions as well as all the information about the qsort issues. Did you ever publish your changes as a patch, or create a write up about what was necessary to create a reproducible build? I would be interested to see wha

Re: gcc-4.9.1 generating different code between two successive builds

HI Martin, Thanks very much for the suggestions as well as all the information about the qsort issues. Did you ever publish your changes as a patch, or create a write up about what was necessary to create a reproducible build? I would be interested to see what others have done, and potentially an

Re: gcc-4.9.1 generating different code between two successive builds

On 12/20/2015 11:39 PM, Cole wrote: Hi, I am busy trying to generate a package for gcc that is consistent between two successive builds, and I am now down to the final few files. I am stuck with the file: cilk-abi-cilk-for.o, which is obviously built with -O2, but between two successive builds,

gcc-4.9.1 generating different code between two successive builds

Hi, I am busy trying to generate a package for gcc that is consistent between two successive builds, and I am now down to the final few files. I am stuck with the file: cilk-abi-cilk-for.o, which is obviously built with -O2, but between two successive builds, the assembly code generated is differ