summaryrefslogtreecommitdiffstats
path: root/llvm/test/Object/archive-replace-pos.test
Commit message (Collapse)AuthorAgeFilesLines
* Replace archive members in the old position.Rafael Espindola2013-07-221-0/+3
| | | | | | | | | | | | This matches gnu archive behavior and since archive member order can change which member is used, not changing the order on replacement looks like the right thing to do. This patch also refactors the logic for which archive member to keep and whether to move it to a helper function (computeInsertAction). The nesting in computeNewArchiveMembers was getting a bit confusing. llvm-svn: 186829
* Don't depend on a llvm-ar specific behavior.Rafael Espindola2013-07-221-1/+2
| | | | | | | | GNU ar when not given the a or b modifiers replaces archive members in the same location of the old ones. I am about to implement that in llvm-ar. For now, just don't depend on the current llvm-ar behavior on this test. llvm-svn: 186823
* Handle replacement into a position past the original member.Rafael Espindola2013-07-211-0/+13
| | | | | | | We were incorrectly computing where to insert a member if it was replacing a previous member that was before the insert point. llvm-svn: 186792
* Fix inserting new elements in a specified location.Rafael Espindola2013-07-191-0/+13
We were only handling the 'a' and 'b' options during moves before. llvm-svn: 186721
OpenPOWER on IntegriCloud