David Blaikie 1d4f28c6bc Remove StringMap::GetOrCreateValue in favor of StringMap::insert ... Having two ways to do this doesn't seem terribly helpful and consistently using the insert version (which we already has) seems like it'll make the code easier to understand to anyone working with standard data structures. (I also updated many references to the Entry's key and value to use first() and second instead of getKey{Data,Length,} and get/setValue - for similar consistency) Also removes the GetOrCreateValue functions so there's less surface area to StringMap to fix/improve/change/accommodate move semantics, etc. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@222319 91177308-0d34-0410-b5e6-96231b3b80d8		2014-11-19 05:49:42 +00:00
..
CMakeLists.txt
LLVMBuild.txt	Attempt at fixing the windows dll build.	2014-07-30 23:39:30 +00:00
LTOCodeGenerator.cpp	libLTO: Assert if LTOCodeGenerator and LTOModule are from different contexts	2014-11-11 23:13:10 +00:00
LTOModule.cpp	Remove StringMap::GetOrCreateValue in favor of StringMap::insert	2014-11-19 05:49:42 +00:00
Makefile