These tests require x86-registered-target, but they don't force the target as
x86 on the command line, which means they will be run and they might fail when
building the x86 backend on another platform (such as AArch64).
Fixes PR28797
Paths
| Differential D23054
[clang-cl] Fix PCH tests to use x86_64 as target ClosedPublic Authored by rovka on Aug 2 2016, 1:13 AM.
Details Summary These tests require x86-registered-target, but they don't force the target as Fixes PR28797
Diff Detail Event Timelinerovka updated this object. Comment Actions This seems to be the case for other similar tests as well (e.g. cl-pch-errorhandling.cpp requires x86-registered-target, but doesn't force it on the command line), but they're not currently crashing. I can update those as well if people think it's the right thing to do. Comment Actions All tests should have the target explicit, so I'd advocate for all of them to be changed. Also, we need to make sure --target=x86_64 is enough on Windows. I remember some -target=arm not being enough (arm-eabi was enough, for some reason). Comment Actions
Coming right up...
It's enough, I've seen it used in other clang-cl tests. rovka retitled this revision from [clang-cl] Fix 2 pch tests to use x86_64 as target to [clang-cl] Fix PCH tests to use x86_64 as target. Comment ActionsAdded cl-pch-errorhandling.cpp This revision is now accepted and ready to land.Aug 2 2016, 6:50 AM Closed by commit rL277457: [clang-cl] Fix PCH tests to use x86_64 as target (authored by rovka). · Explain WhyAug 2 2016, 7:00 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 66467 test/Driver/cl-pch-errorhandling.cpp
test/Driver/cl-pch-search.cpp
test/Driver/cl-pch-showincludes.cpp
|