Fix non-determinism in DAGISel emitter.
authorDaniel Dunbar <daniel@zuster.org>
Sun, 23 Aug 2009 09:47:37 +0000 (09:47 +0000)
committerDaniel Dunbar <daniel@zuster.org>
Sun, 23 Aug 2009 09:47:37 +0000 (09:47 +0000)
commit6f5cc82686d6f25abc3e373b241bc2cb47d87268
tree54e5b716fdbf77f00cc5dba93006c1fa825fab98
parentae60324d465496f18cdd9b5f733d305ebefb0d1e
Fix non-determinism in DAGISel emitter.
 - This manifested as non-determinism in the .inc output in rare cases (when two
   distinct patterns ended up being equivalent, which is rather rare). That
   meant the pattern matching was non-deterministic, which could eventually mean
   the code generator selected different instructions based on the arch.

 - It's probably worth making the DAGISel ensure a total ordering (or force the
   user to), but the simple fix here is to totally order the Record* maps based
   on a unique ID.

 - PR4672, PR4711.

Yay:
--
ddunbar@giles:~$ cat ~/llvm.obj.64/lib/Target/*/*.inc | shasum
d1099ff34b21459a5a3e7021c225c080e6017ece  -
ddunbar@giles:~$ cat ~/llvm.obj.ppc/lib/Target/*/*.inc | shasum
d1099ff34b21459a5a3e7021c225c080e6017ece  -
--

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@79846 91177308-0d34-0410-b5e6-96231b3b80d8
utils/TableGen/CodeGenDAGPatterns.cpp
utils/TableGen/CodeGenDAGPatterns.h
utils/TableGen/Record.cpp
utils/TableGen/Record.h