search for: 12_global__n_1

...b_Support_CrashRecoveryContext.cpp_00000000_A7307A7424CrashRecoveryContextImplEEE >> > Urgh, are we using random elements in the unnamed namespace symbol > generation? This is definitely not the direct output of clang. We mangle anonymous namespaces the same way that GCC does, i.e. 12_GLOBAL__N_1. If there's a compiler that mangles filenames into anonymous namespace names — or anything later in the toolchain which does it — I'm not aware of it. Erik, what compiler are you using? John.

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 > <

Hello LLVM'ers 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: 248400,248403c248400,248403 <