← Back to context Comment by edgyquant 2 years ago That sounds like runtime differences not a difference between two binaries 2 comments edgyquant Reply stcg 2 years ago The difference in binaries must be caused by some runtime difference of a compiler. drdrey 2 years ago That's right, look at this thread for example:https://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20...The Global Value Numbering pass in LLVM was iterating over `DenseMap<BasicBlock*, ...>`, so the iteration order was dependent on the value of BasicBlock pointers. This could lead to the same source files and compiler producing different binaries.
stcg 2 years ago The difference in binaries must be caused by some runtime difference of a compiler. drdrey 2 years ago That's right, look at this thread for example:https://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20...The Global Value Numbering pass in LLVM was iterating over `DenseMap<BasicBlock*, ...>`, so the iteration order was dependent on the value of BasicBlock pointers. This could lead to the same source files and compiler producing different binaries.
drdrey 2 years ago That's right, look at this thread for example:https://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20...The Global Value Numbering pass in LLVM was iterating over `DenseMap<BasicBlock*, ...>`, so the iteration order was dependent on the value of BasicBlock pointers. This could lead to the same source files and compiler producing different binaries.
The difference in binaries must be caused by some runtime difference of a compiler.
That's right, look at this thread for example:
https://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20...
The Global Value Numbering pass in LLVM was iterating over `DenseMap<BasicBlock*, ...>`, so the iteration order was dependent on the value of BasicBlock pointers. This could lead to the same source files and compiler producing different binaries.