[android] Switch armv7 vendor to 'unknown' in target triple to match other arches#34919
[android] Switch armv7 vendor to 'unknown' in target triple to match other arches#34919compnerd merged 1 commit intoswiftlang:mainfrom
Conversation
…other arches Recent changes have made 'none' and 'unknown' not interchangeable anymore, so standardize on 'unknown' for armv7 too.
|
It should have been @swift-ci please test |
|
Build failed |
|
Linux passes, mac single test failure is unrelated, and Windows CI fails when checking out git. |
|
@swift-ci please test macOS platform |
|
@swift-ci please test Windows platform |
compnerd
left a comment
There was a problem hiding this comment.
Yes please. I think that as long as the build succeeds with this change, this is something we should get merged right away. The only concern is with the tool prefixing that might happen in some cases (with the NDK toolchain).
|
@swift-ci please test Windows platform |
|
@swift-ci please test macOS platform |
|
Build failed |
|
Mac CI dies when cross-compiling stdlib for Mac-ARM64, running out of memory? Unrelated to this pull of course.
If you're talking about NDK paths that use these variables, I just checked and they don't. There is a separate |
|
Ping, we should get this in. |
|
@swift-ci please test macOS platform |
|
Build failed |
|
Yet another spurious failure on the Mac CI. |
|
@swift-ci please test macOS platform |
|
I believe that this is safe and everyone is in agreement here, merging. |
Recent changes have made 'none' and 'unknown' not interchangeable anymore, so standardize on 'unknown' for armv7 too.
I don't know exactly when this change was introduced in trunk, maybe with #31170, but both vendors work with the release/5.3 branch. When I just tried to cross-compile the corelibs for armv7 with #33724, where I use 'unknown' in the triple, applied to the Nov. 26 trunk source snapshot, I hit this error when CMake checks that the Swift compiler works when configuring libdispatch, which this pull fixes:
Another way to reproduce is by trying to cross-compile a "hello world" executable by using the Android cross-compilation flags from the docs:
I've modified a couple armv7 tests to use the new vendor, while leaving in others that are meant to check that the vendor and triple are changed before being passed to the linker.
@drodriguez and @compnerd, I'm not sure why these tests on the Android CI didn't catch this, should I add a test that does?