Duncan Sands bcc2393369 Fix the ValueMap copy constructor. The issue is that the map keys are value ... handles with a pointer to the containing map. When a map is copied, these pointers need to be corrected to point to the new map. If not, then consider the case of a map M1 which maps a value V to something. Create a copy M2 of M1. At this point there are two value handles on V, one representing V as a key in M1, the other representing V as a key in M2. But both value handles point to M1 as the containing map. Now delete V. The value handles remove themselves from their containing map (which destroys them), but only the first value handle is successful: the second one cannot remove itself from M1 as (once the first one has removed itself) there is nothing there to remove; it is therefore not destroyed. This causes an assertion failure "All references to V were not removed?". git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@109851 91177308-0d34-0410-b5e6-96231b3b80d8		2010-07-30 05:49:32 +00:00
..
llvm	Fix the ValueMap copy constructor. The issue is that the map keys are value	2010-07-30 05:49:32 +00:00
llvm-c	start straightening out libedis's dependencies and make it fit	2010-07-20 18:25:19 +00:00