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 v
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 v
Well,
that's not exactly what I meant. In gcc, if you use -flto a c file
compiled twice leads to different binaries, if you don't add
-frandom-seed=.
clang also supports the switch -frandom-seed=, but the object
files produced by clang are always binary equal.
Meanwhile I think clang intor
