diff options
| author | Jordan Rupprecht <rupprecht@google.com> | 2019-02-07 16:41:06 +0000 |
|---|---|---|
| committer | Jordan Rupprecht <rupprecht@google.com> | 2019-02-07 16:41:06 +0000 |
| commit | bf990ab5aab03aa0aac53c9ef47ef264307804ed (patch) | |
| tree | 2741b685b47afa28bba455256956be1f837cca75 /lldb/packages/Python/lldbsuite/test/functionalities/command_source/my.py | |
| parent | b88144e4babdb1acc2694010de377f826242e731 (diff) | |
| download | bcm5719-llvm-bf990ab5aab03aa0aac53c9ef47ef264307804ed.tar.gz bcm5719-llvm-bf990ab5aab03aa0aac53c9ef47ef264307804ed.zip | |
[llvm-ar][libObject] Fix relative paths when nesting thin archives.
Summary:
When adding one thin archive to another, we currently chop off the relative path to the flattened members. For instance, when adding `foo/child.a` (which contains `x.txt`) to `parent.a`, when flattening it we should add it as `foo/x.txt` (which exists) instead of `x.txt` (which does not exist).
As a note, this also undoes the `IsNew` parameter of handling relative paths in r288280. The unit test there still passes.
This was reported as part of testing the kernel build with llvm-ar: https://patchwork.kernel.org/patch/10767545/ (see the second point).
Reviewers: mstorsjo, pcc, ruiu, davide, david2050
Subscribers: hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D57842
llvm-svn: 353424
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/command_source/my.py')
0 files changed, 0 insertions, 0 deletions
