[swift-dev] Swift CI updated with Xcode 7.3

All of the OS X bots on ci.swift.org were updated with Xcode 7.3 . https://developer.apple.com/xcode/download/ Thanks, Mishal Shah___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailm

Re: [swift-dev] ObjC Interoperability under armv7--linux-gnueabi

> The implementation of our ObjC interop makes pretty deep invasive assumptions > about the Apple ObjC runtime ABI as well as the implementation of classes in > Cocoa. It probably needs to be rewritten from the ground up to support > another runtime and Foundation implementation. > > -Joe Alas,

Re: [swift-dev] ObjC Interoperability under armv7--linux-gnueabi

> On Mar 29, 2016, at 1:03 PM, Iliya Trub via swift-dev > wrote: > > Dear colleagues > Ihave built swiftc, libswiftCore.so and other outputs under > armv7--linux-gnueabi with open source ObjC-runtime and enabled ObjC interop. > I linked the simplest swift-application, which creates the instan

[swift-dev] Pull requests for Swift 2.2.1

Hi everyone, For those of you creating pull requests for Swift 2.2.1, please do the following: - Add the ‘Swift 2.2.x’ milestone in the pull request. - Assign the pull request to me. - Optionally: Put "[Swift 2.2.1]” in the pull request title. Thanks! Ted___

Re: [swift-dev] ObjC Interoperability under armv7--linux-gnueabi

I emitted with -fobjc-runtime=gnustep. 29.03.2016, 23:13, "Philippe Hausler" : > I would guess that you are emitting with the wrong runtime personality (iirc > linux defaults to fragile (objc1) GNU objc runtime). You might need to muck > about with flags, most notably -fobjc-runtime. That being

Re: [swift-dev] ObjC Interoperability under armv7--linux-gnueabi

I’d be interested in the patches. Daniel > On Mar 29, 2016, at 1:03 PM, Iliya Trub via swift-dev > wrote: > > Dear colleagues > Ihave built swiftc, libswiftCore.so and other outputs under > armv7--linux-gnueabi with open source ObjC-runtime and enabled ObjC interop. > I linked the simplest

Re: [swift-dev] ObjC Interoperability under armv7--linux-gnueabi

I would guess that you are emitting with the wrong runtime personality (iirc linux defaults to fragile (objc1) GNU objc runtime). You might need to muck about with flags, most notably -fobjc-runtime. That being said that path might be filled with other issues beyond just the layout differentials

[swift-dev] ObjC Interoperability under armv7--linux-gnueabi

Dear colleagues Ihave built swiftc, libswiftCore.so and other outputs under armv7--linux-gnueabi with open source ObjC-runtime and enabled ObjC interop. I linked the simplest swift-application, which creates the instance of custom ObjC-class and call instance-method of it. If somebody interested

Re: [swift-dev] Requiring Xcode 7.3 to build Swift master for Apple platforms?

> On Mar 29, 2016, at 11:29 AM, Andrew Hyatt wrote: > > Agreed. The minimum OS X version for Xcode 7.3 is 10.11.0, which would make > El Capitan required to run Swift 3.0. If Xcode 7.3 requires 10.11, I'd say it's likely that the version of Xcode that includes Swift 3 will need to be hosted o

Re: [swift-dev] Requiring Xcode 7.3 to build Swift master for Apple platforms?

On Tue, Mar 29, 2016 at 11:29 AM, Andrew Hyatt via swift-dev wrote: > Agreed. The minimum OS X version for Xcode 7.3 is 10.11.0, which would make > El Capitan required to run Swift 3.0. Swift deploys back to OS X 10.9. We're only talking about developers. Dmitri -- main(i,j){for(i=2;;i++){fo

Re: [swift-dev] Requiring Xcode 7.3 to build Swift master for Apple platforms?

Agreed. The minimum OS X version for Xcode 7.3 is 10.11.0, which would make El Capitan required to run Swift 3.0. - Andrew Hyatt ahyatt...@icloud.com > On Mar 29, 2016, at 11:23, David Abraham via swift-dev > wrote: > > Would this be a temporary limitation? I'd prefer to see Swift available

Re: [swift-dev] Requiring Xcode 7.3 to build Swift master for Apple platforms?

Would this be a temporary limitation? I'd prefer to see Swift available to any development environment even on Apple Platforms. It contributes to the message of openness. -Dave Enviado desde mi iPhone > El mar 29, 2016, a las 2:02 PM, Joe Groff via swift-dev > escribió: > > Xcode 7.3 inc

[swift-dev] Requiring Xcode 7.3 to build Swift master for Apple platforms?

Xcode 7.3 included a fix for the Apple linker that's necessary to support some of the metadata format changes we're making in Swift 3. I have some workarounds in place that I'd like to remove since they suppress linker coalescing of some constant strings. Would anyone object to us requiring usin

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3038

/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swift/test/Interpreter/Inputs/ImportAsMember/IAMVec.c:2:10: fatal error: 'math.h' file not found #include Err, is there something dramatically different about the builder than my system here? > On Mar 29, 2016, at 10:01 AM, no-re

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3038

I pushed a fix. > On Mar 29, 2016, at 10:02 AM, Michael Ilseman via swift-dev > wrote: > > /Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swift/test/Interpreter/Inputs/ImportAsMember/IAMVec.c:2:10: > fatal error: 'math.h' file not found > #include > > Err, is there somethi

Re: [swift-dev] Swift kernel hacking, compiler options and target triples

> On 28 Mar 2016, at 22:20, Greg Parker wrote: > > swiftc has a hidden -Xllvm flag that passes options to the LLVM code > generator. That might work for low-level options like instruction selection > and maybe the red zone. It's not the right answer for production use, but it > might be good