I have a solution, stay tuned.
So it turns out since the clang driver has special behavior on Darwin for
handling Universal apps, there is a different code path that happens during
BuildActions. clang::driver::Driver::BuildUniversalActions is called instead of
BuildActions on Darwin, and what
Looking into this. Thanks for the heads up.
PL
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Wednesday, November 20, 2019 4:12 PM, Alex L wrote:
> Hi Puyan,
>
> This commit caused two Clang failures on Darwin:
>
> Clang :: InterfaceStubs/merge-conflict-test.c
Hi Puyan,
This commit caused two Clang failures on Darwin:
Clang :: InterfaceStubs/merge-conflict-test.c
Clang :: InterfaceStubs/object-float.c
Here's the build log from out bot:
http://lab.llvm.org:8080/green/job/clang-stage1-RA/3929/console
Can you please resolve the issue with the
Author: Puyan Lotfi
Date: 2019-11-20T16:22:50-05:00
New Revision: 73429126c91c2065c6f6ef29b3eec1b7798502bb
URL:
https://github.com/llvm/llvm-project/commit/73429126c91c2065c6f6ef29b3eec1b7798502bb
DIFF:
https://github.com/llvm/llvm-project/commit/73429126c91c2065c6f6ef29b3eec1b7798502bb.diff