| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 135375
|
| |
|
|
|
|
|
|
|
| |
vec.insert(vec.begin(), vec[3]);
The issue was that vec[3] returns a reference into the vector, which is invalidated when insert() memmove's the elements down to make space. The method needs to specifically detect and handle this case to correctly match std::vector's semantics.
Thanks to Howard Hinnant for clarifying the correct behavior, and explaining how std::vector solves this problem.
llvm-svn: 134554
|
| |
|
|
|
|
| |
until other LLVM projects using these are cleaned up.
llvm-svn: 117200
|
| |
|
|
| |
llvm-svn: 111539
|
| |
|
|
| |
llvm-svn: 99633
|
| |
|
|
|
|
|
| |
aligned storage, the capacity may be more than what is explicitly
requested.
llvm-svn: 98846
|
| |
|
|
|
|
|
| |
- These allow clients to make use of the extra elements in the vector which
have already been allocated, without requiring them to be value initialized.
llvm-svn: 79433
|
| |
|
|
| |
llvm-svn: 75422
|
| |
|
|
| |
llvm-svn: 69846
|
| |
|
|
| |
llvm-svn: 62035
|
|
|
llvm-svn: 62025
|