summaryrefslogtreecommitdiffstats
path: root/llvm/test
diff options
context:
space:
mode:
authorPetr Hosek <phosek@chromium.org>2019-04-29 20:04:20 +0000
committerPetr Hosek <phosek@chromium.org>2019-04-29 20:04:20 +0000
commit497216487199d74e51b413720e85390e63e620fd (patch)
tree927e4ad2daff9c97c3ccea888ccf675c33b71e96 /llvm/test
parent8dea9cda2ee6de23b2467d7ad29186a16fe14dc1 (diff)
downloadbcm5719-llvm-497216487199d74e51b413720e85390e63e620fd.tar.gz
bcm5719-llvm-497216487199d74e51b413720e85390e63e620fd.zip
[gn] Use label_name rather than target_output_name for objects
Multiple targets in the same output directory can use the same target_output_name. The typical example of that is having a shared and a static library of the same, e.g. libc++.so and libc++.a. When that's the case, the object files produced for each target are going to conflict. Using the label_name avoids this conflict since labels are guaranteed to be unique within a single BUILD.gn file which corresponds to a single output directory. Differential Revision: https://reviews.llvm.org/D60329 llvm-svn: 359494
Diffstat (limited to 'llvm/test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud