llvm-6502/tools/yaml2obj
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
Makefile
yaml2coff.cpp yaml2obj, COFF: Consider the DOS stub when laying out section headers 2014-11-15 02:03:59 +00:00
yaml2elf.cpp Remove StringMap::GetOrCreateValue in favor of StringMap::insert 2014-11-19 05:49:42 +00:00
yaml2obj.cpp Modernize raw_fd_ostream's constructor a bit. 2014-08-25 18:16:47 +00:00
yaml2obj.h