-
Notifications
You must be signed in to change notification settings - Fork 195
Support for cross-compiling the swift repl #48
Conversation
(requires new build-script variable: LLDB_SWIFTC)
@swift-ci Please test Linux platform |
It will fail to build until the requisite swift build-script variables are given (see linked patch). |
Ah I see, okay thanks. Separately, I have a question into our build system maintainer to figure out why said build did not actually kick off, independently of its expectation to fail. (We should have gotten a notification of a build going into a queue). |
@tfiala we have cross-repo testing support now, so it should work |
@swift-ci Please test Linux platform |
Buidbot failed to pull in the linked patch to the swift build script, so it failed. CC @shahmishal , is this supposed to work? |
We're seeing this build error on the Linux CI:
|
I should have it completed by end of day today. |
Ah sorry, missed that before I reflected up the error. |
swiftlang/swift#4574 |
Please test with following PR: @swift-ci Please test Linux platform |
@shahmishal, this doesn't look like it worked. I'm seeing the same error we were getting this morning. |
The tests from the swift side of the patch seem to work: https://ci.swift.org/job/swift-PR-Linux/3718/consoleFull
It's a little bit hard to follow because there's loads of changes that went in to the same test (and because it was done from the swift side, the swift project is listed in Jenkins' list of changes but the LLDB one isn't). But I think we ended up with everything where it should be. EDIT: Oops. Looking at it again, we didn't even build LLDB :p
|
Ah okay thanks! |
Please test with following PR: @swift-ci Please test Linux platform |
It picked up the right PR, lets see if we see any other issues.
|
Okay, fingers crossed :-) |
it passed 👍 |
Awesome, thanks! |
@shahmishal I think I put this in prematurely. We need swiftlang/swift#4574 to go in first, don't we. |
I took care of the other check-in. I restarted the LLDB builders to make sure they picked up the swift change. |
This reverts commit rL280668 because the register tests fail on i386 Linux. I investigated a little bit what causes the failure - there are missing registers when running 'register read -a'. This is the output I got at the bottom: """ ... Memory Protection Extensions: bnd0 = {0x0000000000000000 0x0000000000000000} bnd1 = {0x0000000000000000 0x0000000000000000} bnd2 = {0x0000000000000000 0x0000000000000000} bnd3 = {0x0000000000000000 0x0000000000000000} unknown: 2 registers were unavailable. """ Also looking at the packets exchanged between the client and server: """ ... history[308] tid=0x7338 < 19> send packet: $qRegisterInfo4a#d7 history[309] tid=0x7338 < 130> read packet: $name:bnd0;bitsize:128;offset:1032;encoding:vector;format:vector-uint64;set:Memory Protection Extensions;ehframe:101;dwarf:101;#48 history[310] tid=0x7338 < 19> send packet: $qRegisterInfo4b#d8 history[311] tid=0x7338 < 130> read packet: $name:bnd1;bitsize:128;offset:1048;encoding:vector;format:vector-uint64;set:Memory Protection Extensions;ehframe:102;dwarf:102;#52 history[312] tid=0x7338 < 19> send packet: $qRegisterInfo4c#d9 history[313] tid=0x7338 < 130> read packet: $name:bnd2;bitsize:128;offset:1064;encoding:vector;format:vector-uint64;set:Memory Protection Extensions;ehframe:103;dwarf:103;#53 history[314] tid=0x7338 < 19> send packet: $qRegisterInfo4d#da history[315] tid=0x7338 < 130> read packet: $name:bnd3;bitsize:128;offset:1080;encoding:vector;format:vector-uint64;set:Memory Protection Extensions;ehframe:104;dwarf:104;#54 history[316] tid=0x7338 < 19> send packet: $qRegisterInfo4e#db history[317] tid=0x7338 < 76> read packet: $name:bndcfgu;bitsize:64;offset:1096;encoding:vector;format:vector-uint8;#99 history[318] tid=0x7338 < 19> send packet: $qRegisterInfo4f#dc history[319] tid=0x7338 < 78> read packet: $name:bndstatus;bitsize:64;offset:1104;encoding:vector;format:vector-uint8;#8e ... """ The bndcfgu and bndstatus registers don't have the 'Memory Protections Extension' set. I looked at the code and it seems that that is set correctly. So I'm not sure what's the problem or where does it come from. Also there is a second failure related to something like this in the tests: """ registerSet.GetName().lower() """ For some reason the registerSet.GetName() returns None. git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@280703 91177308-0d34-0410-b5e6-96231b3b80d8
@tfiala What happened to this? Did it get lost in a merge? Not in |
@llvm-beanz, did we lose this as part of your CMake enhancements, or did this happen as a casualty of a merge? |
I can’t find any indication this was ever on trunk. It certainly wasn’t there before my patch merged in. -Chris
|
Requires new build-script variable:
LLDB_SWIFTC
, from swiftlang/swift#4574