summaryrefslogtreecommitdiffstats
path: root/llvm/unittests/ADT/StringMapTest.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Removing LLVM_DELETED_FUNCTION, as MSVC 2012 was the last reason for ↵Aaron Ballman2015-02-151-4/+4
| | | | | | requiring the macro. NFC; LLVM edition. llvm-svn: 229340
* Remove StringMap::GetOrCreateValue in favor of StringMap::insertDavid Blaikie2014-11-191-6/+4
| | | | | | | | | | | | | | 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. llvm-svn: 222319
* StringMap: Test and finish off supporting perfectly forwarded values in ↵David Blaikie2014-11-141-1/+15
| | | | | | | | StringMap operations. Followup to r221946. llvm-svn: 221958
* Recommit 211309 (StringMap::insert), reverted in 211328 due to issues with ↵David Blaikie2014-06-231-2/+40
| | | | | | | | | | | | private, but non-deleted, move members. Certain versions of GCC (~4.7) couldn't handle the SFINAE on access control, but with "= delete" (hidden behind a macro for portability) this issue is worked around/addressed. Patch by Agustín Bergé llvm-svn: 211525
* Revert "Add StringMap::insert(pair) consistent with the standard associative ↵Rafael Espindola2014-06-201-38/+0
| | | | | | | | | | | | container concept." This reverts commit r211309. It looks like it broke some bots: http://lab.llvm.org:8011/builders/clang-x86_64-ubuntu-gdb-75/builds/15563/steps/compile/logs/stdio llvm-svn: 211328
* Add StringMap::insert(pair) consistent with the standard associative ↵David Blaikie2014-06-191-0/+38
| | | | | | | | container concept. Patch by Agustín Bergé. llvm-svn: 211309
* Convert StringMapEntry::Create to use StringRef instead of start/end ↵Craig Topper2014-06-111-3/+3
| | | | | | pointers. Simpliies all in tree call sites. No functional change. llvm-svn: 210638
* Remove use of = default/= delete as they're unsupported on MSVC2012David Blaikie2014-05-091-4/+9
| | | | llvm-svn: 208388
* Missed formattingDavid Blaikie2014-05-081-11/+11
| | | | llvm-svn: 208362
* StringMap: Move assignment and move construction.David Blaikie2014-05-081-0/+67
| | | | llvm-svn: 208361
* StringMap support for move-only values.David Blaikie2014-05-081-0/+16
| | | | llvm-svn: 208359
* Fix break introduced in r198377 due to using a local type as a template ↵David Blaikie2014-01-031-6/+6
| | | | | | parameter. llvm-svn: 198379
* Test coverage for non-default-constructible elements in a StringMapDavid Blaikie2014-01-021-0/+15
| | | | | | | | | This functionality was enabled by r198374. Here's a test to ensure it works and we don't regress it. Based on a patch by Maciej Piechotka. llvm-svn: 198377
* Remove StringMapEntryInitializer support.David Blaikie2014-01-021-17/+0
| | | | | | | It was never specialized so let's just remove that unused configurability and always do the default. llvm-svn: 198374
* Fix PR13148, an inf-loop in StringMap.Chandler Carruth2012-06-191-0/+22
| | | | | | | | | | | | | | | StringMap suffered from the same bug as DenseMap: when you explicitly construct it with a small number of buckets, you can arrange for the tombstone-based growth path to be followed when the number of buckets was less than '8'. In that case, even with a full map, it would compare '0' as not less than '0', and refuse to grow the table, leading to inf-loops trying to find an empty bucket on the next insertion. The fix is very simple: use '<=' as the comparison. The same fix was applied to DenseMap as well during its recent refactoring. Thanks to Alex Bolz for the great report and test case. =] llvm-svn: 158725
* Remove some superfluous SCOPED_TRACEs from this unit test.Chandler Carruth2012-06-191-6/+0
| | | | | | | GoogleTest already prints errors with all the information about which test case contained the error. llvm-svn: 158724
* The key of a StringMap can contain nul's in it, so having first() returnChris Lattner2011-07-141-3/+3
| | | | | | const char* doesn't make sense. Have it return StringRef instead. llvm-svn: 135167
* Merge System into Support.Michael J. Spencer2010-11-291-1/+1
| | | | llvm-svn: 120298
* Fix (harmless) memory leak found by memcheck.Jeffrey Yasskin2010-02-111-0/+1
| | | | llvm-svn: 95862
* Move DataTypes.h to include/llvm/System, update all users. This breaks the lastChandler Carruth2009-10-261-1/+1
| | | | | | direct inclusion edge from System to Support. llvm-svn: 85086
* Convert StringMap to using StringRef for its APIs.Daniel Dunbar2009-07-231-10/+13
| | | | | | | | | | | | - Yay for '-'s and simplifications! - I kept StringMap::GetOrCreateValue for compatibility purposes, this can eventually go away. Likewise the StringMapEntry Create functions still follow the old style. - NIFC. llvm-svn: 76888
* unbreak unit-tests on gcc-4.4.Torok Edwin2009-07-211-0/+1
| | | | llvm-svn: 76542
* Some generic clean-ups. Also make the StringMapEntryInitializer ↵Bill Wendling2009-01-081-45/+44
| | | | | | specialization apply only to the tests that are actually testing it. llvm-svn: 61923
* * Don't explicitly cast "0" to "void*". This doesn't work well with specializedBill Wendling2009-01-081-3/+17
| | | | | | | | | StringMapEntryInitializer classes. Leave it for the compiler to figure out what the type is and what "0" should be transformed into. * Un-disable the unit tests which test the StringMapEntryInitializer class. llvm-svn: 61922
* 80-column violation fix.Bill Wendling2009-01-081-1/+1
| | | | llvm-svn: 61919
* * Added unittests for StringMapMisha Brukman2009-01-081-0/+189
* Fixed but in StringMap::clear() * Removed trailing whitespace Original patch by Talin. llvm-svn: 61914
OpenPOWER on IntegriCloud