Go to file
Mark Searles 4e3d6160db Use the return value of UpdateNodeOperands(); in some cases, UpdateNodeOperands() modifies the node in-place and using the return value isn’t strictly necessary. However, it does not necessarily modify the node, but may return a resultant node if it already exists in the DAG. See comments in UpdateNodeOperands(). In that case, the return value must be used to avoid such scenarios as an infinite loop (node is assumed to have been updated, so added back to the worklist, and re-processed; however, node hasn’t changed so it is once again passed to UpdateNodeOperands(), assumed modified, added back to worklist; cycle infinitely repeats).
Differential Revision: https://reviews.llvm.org/D38466

llvm-svn: 315957
2017-10-16 23:38:53 +00:00
clang Fix usage in TableGen of getValueAsString 2017-10-16 23:25:24 +00:00
clang-tools-extra [change-namespace] do not change type locs in defaulted functions. 2017-10-16 08:20:10 +00:00
compiler-rt [cfi] Test cross-dso CFI on Android. 2017-10-16 18:03:11 +00:00
debuginfo-tests Revert r313600 due to bot failures on Green Dragon. 2017-09-19 14:51:37 +00:00
libclc travis: enable checks of nvptx libraries 2017-10-10 18:10:25 +00:00
libcxx Fix last_write_time.pass.cpp to work with clang-3.9 and earlier 2017-10-15 21:52:53 +00:00
libcxxabi Fix ASAN build with older compiler-rt versions. 2017-09-14 22:37:34 +00:00
libunwind libunwind: document tested FreeBSD configs and sort OS list 2017-10-14 17:04:04 +00:00
lld COFF: Add resource files to linkrepro instead of the cvtres object file. 2017-10-16 23:15:04 +00:00
lldb The save_crashlog command was still looking at lldb.target and 2017-10-12 02:21:41 +00:00
llgo irgen: Create functions instead of global variables for builtin hash and equal algorithms. 2017-06-04 22:11:28 +00:00
llvm Use the return value of UpdateNodeOperands(); in some cases, UpdateNodeOperands() modifies the node in-place and using the return value isn’t strictly necessary. However, it does not necessarily modify the node, but may return a resultant node if it already exists in the DAG. See comments in UpdateNodeOperands(). In that case, the return value must be used to avoid such scenarios as an infinite loop (node is assumed to have been updated, so added back to the worklist, and re-processed; however, node hasn’t changed so it is once again passed to UpdateNodeOperands(), assumed modified, added back to worklist; cycle infinitely repeats). 2017-10-16 23:38:53 +00:00
openmp KMP_HW_SUBSET vs KMP_PLACE_THREADS rival envirables fix 2017-10-06 19:23:19 +00:00
parallel-libs [Axccel] Remove -Wno-missing-braces in build 2016-12-19 21:34:07 +00:00
polly [Polly] Add XFAIL to large-numbers-in-boundary-context.ll 2017-10-16 15:12:39 +00:00