diff options
| author | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2015-01-12 19:22:04 +0000 |
|---|---|---|
| committer | Duncan P. N. Exon Smith <dexonsmith@apple.com> | 2015-01-12 19:22:04 +0000 |
| commit | 728315adf4c24bd22667401633de9f4ca84389df (patch) | |
| tree | f80ca7811321c4016b908e972b1be75c080f2d4b /lib/IR | |
| parent | 6205b21cf5e597e6ecfcc73d70dc5a830c28df02 (diff) | |
IR: Add test for handleChangedOperand() recursion
Turns out this can happen. Remove the `FIXME` and add a testcase that
crashes without the extra logic.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@225657 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/IR')
| -rw-r--r-- | lib/IR/Metadata.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/lib/IR/Metadata.cpp b/lib/IR/Metadata.cpp index 1ae9a96fe46..baa0b78762c 100644 --- a/lib/IR/Metadata.cpp +++ b/lib/IR/Metadata.cpp @@ -537,8 +537,6 @@ void GenericMDNode::handleChangedOperand(void *Ref, Metadata *New) { if (InRAUW) { // We just hit a recursion due to RAUW. Set the operand and move on, since // we're about to be deleted. - // - // FIXME: Can this cycle really happen? setOperand(Op, New); return; } |