Re: [swift-dev] What do to when stdlib guidelines conflict with proposal?

> On May 12, 2016, at 9:16 PM, Russ Bishop wrote: > > >> On May 12, 2016, at 8:33 AM, Joe Groff > > wrote: >> >> We might want to wait till we review Andy's UnsafeBytePointer proposal. If >> we accept that, it will separate UnsafePointer into its own type. >> >> -Joe

Re: [swift-dev] What do to when stdlib guidelines conflict with proposal?

> On May 12, 2016, at 8:33 AM, Joe Groff wrote: > > We might want to wait till we review Andy's UnsafeBytePointer proposal. If we > accept that, it will separate UnsafePointer into its own type. > > -Joe Fair enough; I can hold off on this branch until then. Russ

Re: [swift-dev] How to run the tests out-of-tree?

On Thu, May 12, 2016 at 7:24 PM, Karl Wagner wrote: > I’m cross-compiling a native compiler. That is to say, I’m not building a > cross-compiler in the way we build for Android or iOS: a native compiler with > foreign standard libraries. Both the compiler and stdlib are foreign to the > build m

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 18:56, Andrew Trick wrote: > >> - What was the thought behind putting UnsafeBytePointer in PointerTypeKind? >> OpaquePointer isn’t there, and I’m concerned about places that test if >> something’s a pointer by checking that the pointee type is non-null (by far >> the com

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 18:34, Andrew Trick wrote: > >> - On the flip side, I think we do need to preserve the ability to >> reference-cast in order to send Objective-C messages, at least for now. I >> don’t know how I want to expose that to users, though. (In general it’s >> probably worth see

Re: [swift-dev] How to run the tests out-of-tree?

I’m cross-compiling a native compiler. That is to say, I’m not building a cross-compiler in the way we build for Android or iOS: a native compiler with foreign standard libraries. Both the compiler and stdlib are foreign to the build machine. I’d like to produce an installable package (that muc

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 9:27 AM, Jordan Rose wrote: > > Thoughts on the diff: https://github.com/atrick/swift/tree/unsafeptr_convert > - What was the thought behind putting UnsafeBytePointer in PointerTypeKind? > OpaquePointer isn’t ther

Re: [swift-dev] How to run the tests out-of-tree?

On Thu, May 12, 2016 at 6:33 PM, Karl Wagner via swift-dev wrote: > My original idea was a lot simpler - create a script grabbing the specific > executables we need (FileCheck, llvm-link, etc) and the tests, package it > up, ship it out via ssh and run it on the intended target, piping the output

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 9:27 AM, Jordan Rose wrote: > > On the model itself: Responding to your feedback on the model (thanks!). https://github.com/atrick/swift/blob/type-safe-mem-docs/docs/TypeSafeMemory.rst With

Re: [swift-dev] How to run the tests out-of-tree?

> On 13 May 2016, at 02:36, Greg Parker wrote: > > >> On May 12, 2016, at 7:45 AM, Karl via swift-dev > > wrote: >> >> So I’ve been working on cross-compiling for ARM, and it seems pretty good - >> only a bit of refactoring of the build script really needed. It’s a

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 15.10 (master) #5000

I'm not sure where the resiliency work stands, but I wonder if we've caught incremental-compilation issue here? I added a field to XCTestCase, TestFoundation which links to XCTest.so wasn't recompiled at all, and proceeded to crash upon launch. torsdag 12 maj 2016 skrev : > [FAILURE] oss-swift-in

Re: [swift-dev] How to run the tests out-of-tree?

> On May 12, 2016, at 7:45 AM, Karl via swift-dev wrote: > > So I’ve been working on cross-compiling for ARM, and it seems pretty good - > only a bit of refactoring of the build script really needed. It’s a popular > request, the lack of which is hindering lots of people and businesses who >

[swift-dev] swift-3.0-preview-1-branch has been cut

Hello everyone. We have cut the swift-3.0-preview-1-branch. Any changes to that branch need to go through pull requests, and be approved by the release manager. For more details on the Swift 3.0 Release Process, please check out the blog post: https://swift.org/blog/swift-3-0-release-proces

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 15.10 (master) #5000

[+swift-corelibs-dev] I don't think Foundation even tries to do incremental builds. I wonder if XCTest.so needs to be marked as a dependency somewhere in the higher-level build system. Jordan > On May 12, 2016, at 15:52, Brian Croom wrote: > > I'm not sure where the resiliency work stands, bu

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 3:21 PM, Joe Groff wrote: >> On May 12, 2016, at 11:21 AM, John McCall wrote: >> >>> On May 12, 2016, at 10:45 AM, Jordan Rose via swift-dev >>> wrote: On May 12, 2016, at 10:44, Joe Groff wrote: > On May 12, 2016, at 9:27 AM, Jordan Rose via swift-d

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 11:21 AM, John McCall wrote: > >> On May 12, 2016, at 10:45 AM, Jordan Rose via swift-dev >> wrote: >>> On May 12, 2016, at 10:44, Joe Groff wrote: >>> >>> On May 12, 2016, at 9:27 AM, Jordan Rose via swift-dev wrote: - I’m uncomfortable wi

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 11:21 AM, John McCall via swift-dev > wrote: > > Well, we can say "A program has undefined behavior if it does X or Y", or we > can say "A program which does X or Y lacks type safety". In all cases we are > referring to a concept defined elsewhere. If we say "undefined

Re: [swift-dev] Support for building without the stdlib

On Thu, May 12, 2016 at 1:07 PM, Vedant Kumar via swift-dev wrote: > Hi, > > I have a build preset which omits "stdlib;sdk-overlay" from > swift-install-components. > > After 6670bb76, this preset triggers a swift cmake failure (Unknown build > type). Is it no longer allowed to build swift witho

[swift-dev] Support for building without the stdlib

Hi, I have a build preset which omits "stdlib;sdk-overlay" from swift-install-components. After 6670bb76, this preset triggers a swift cmake failure (Unknown build type). Is it no longer allowed to build swift without the stdlib? thanks vedant ___ sw

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 10:45 AM, Jordan Rose via swift-dev > wrote: >> On May 12, 2016, at 10:44, Joe Groff > > wrote: >> >> >>> On May 12, 2016, at 9:27 AM, Jordan Rose via swift-dev >> > wrote: >>> >>> >>> - I’m uncomfortable with using th

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 10:44, Joe Groff wrote: > > >> On May 12, 2016, at 9:27 AM, Jordan Rose via swift-dev > > wrote: >> >> >> - I’m uncomfortable with using the term “undefined behavior” as if it’s >> universally understood. Up until now we haven't formally had

Re: [swift-dev] [RFC] UnsafeBytePointer API for In-Memory Layout

> On May 12, 2016, at 9:27 AM, Jordan Rose via swift-dev > wrote: > > > - I’m uncomfortable with using the term “undefined behavior” as if it’s > universally understood. Up until now we haven't formally had that notion in > Swift, just “type safety” and “memory safety” and “invariant-preserv

Re: [swift-dev] How to run the tests out-of-tree?

Hi, Karl. I don’t think it would be too hard to handle most of them. The tests are actually pretty standalone: they require the LLVM tool “lit ” (in llvm/utils/lit/) and some helper tools from the build directory like “FileCheck” and “not”. To run the

Re: [swift-dev] What do to when stdlib guidelines conflict with proposal?

> On May 11, 2016, at 10:18 PM, Chris Lattner via swift-dev > wrote: > > On May 11, 2016, at 8:17 PM, Russ Bishop via swift-dev > wrote: >> >>> On May 11, 2016, at 4:50 PM, Dmitri Gribenko wrote: >>> >>> On Wed, May 11, 2016 at 2:53 PM, Russ Bishop via swift-dev >>> wrote: I’m implem

[swift-dev] How to run the tests out-of-tree?

Hi So I’ve been working on cross-compiling for ARM, and it seems pretty good - only a bit of refactoring of the build script really needed. It’s a popular request, the lack of which is hindering lots of people and businesses who would like to experiment with swift on their ARM-based devices. T