[swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #359

Title: Report [FAILURE] oss-swift-package-osx [#359] Build URL:https://ci.swift.org/job/oss-swift-package-osx/359/ Project:oss-swift-package-osx Date of build:Mon, 25 Sep 2017 23:51:40 -0500 Build duration:1 hr 39 min Identified problems:Regression test failed: This build

Re: [swift-dev] [Swift CI] Build Failure: 1. OSS - Swift ASAN - OS X (master) #293

This should fix it: https://github.com/apple/swift/pull/12119 Slava > On Sep 25, 2017, at 9:55 PM, Slava Pestov via swift-dev > wrote: > > This is from my changes. I think I know what the problem is, I’ll test a fix > now. > > Slava > >> On Sep 2

Re: [swift-dev] Adding a field to StrongRefCount class

> On Sep 26, 2017, at 12:56 AM, Jiho Choi via swift-dev > wrote: > I want to add a field to StrongRefCount class for some experiment, but the > build fails while building self-hosted 'swift-build'. I am using the version > 3.1.1. > > Does the shape of StrongRefCount class have any implicit de

Re: [swift-dev] Metadata Representation

> On Sep 26, 2017, at 12:35 AM, Saleem Abdulrasool > wrote: > On Mon, Sep 25, 2017 at 11:47 AM, John McCall > wrote: > > On Sep 25, 2017, at 12:24 PM, Joe Groff > > wrote: > >> On Sep 24, 2017, at 10:30 PM, John McCall >>

[swift-dev] Adding a field to StrongRefCount class

Hi, I want to add a field to StrongRefCount class for some experiment, but the build fails while building self-hosted 'swift-build'. I am using the version 3.1.1. Does the shape of StrongRefCount class have any implicit dependence on other parts of the runtime? What is the correct way to add a

Re: [swift-dev] [Swift CI] Build Failure: 1. OSS - Swift ASAN - OS X (master) #293

This is from my changes. I think I know what the problem is, I’ll test a fix now. Slava > On Sep 25, 2017, at 9:38 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-ASAN-RA-osx [#293] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-ASAN-RA-osx/293/ >

Re: [swift-dev] Metadata Representation

On Mon, Sep 25, 2017 at 11:47 AM, John McCall wrote: > > On Sep 25, 2017, at 12:24 PM, Joe Groff wrote: > >> On Sep 24, 2017, at 10:30 PM, John McCall wrote: > >>> On Sep 22, 2017, at 8:39 PM, Saleem Abdulrasool > wrote: > >>> > >>> On Thu, Sep 21, 2017 at 10:28 PM, John McCall > wrote: > >>>

Re: [swift-dev] A constraint system / type variable question

> On Sep 25, 2017, at 21:59, Joe Groff via swift-dev > wrote: > > > > On Sep 25, 2017, at 3:41 PM, David Zarzycki > wrote: > >> >> >>> On Sep 25, 2017, at 18:23, Joe Groff >> > wrote: >>> >>> >>> On Sep 25, 2017, at 1:04 PM, David Zarz

Re: [swift-dev] A constraint system / type variable question

> On Sep 25, 2017, at 3:41 PM, David Zarzycki wrote: > > > >>> On Sep 25, 2017, at 18:23, Joe Groff wrote: >>> >>> >>> >>> On Sep 25, 2017, at 1:04 PM, David Zarzycki wrote: >>> >>> >>> On Sep 25, 2017, at 14:37, Joe Groff wrote: > On Sep 23, 2017, at 10:36

Re: [swift-dev] Thoughts on a hypothetical "Multiple primary file" mode

Thank you, Jordan. Lots to mull over for me here. BTW, although it was I who mentioned "multiple primary files" today, it was not my idea. I was relaying what Graydon had mentioned. (Just to give credit where it's due.) - David > On Sep 25, 2017, at 3:45 PM, Jordan Rose wrote: > > Hi, all. Da

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 14.04 - Long Test (master) #799

I don't think this is related to my commit -- I've just touched docs and llvm-cov. vedant > On Sep 25, 2017, at 5:51 PM, no-re...@swift.org wrote: > > New issue found! > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04-long-test [#799] > > Build URL: > https://ci.swift.org/job/oss-

[swift-dev] backporting clang patches from upstream?

Hi, I'd like to backport the following commit to swift-clang https://github.com/llvm-mirror/clang/commit/5c5aea8028aa58b347eaf3b552bc158a2a85ee18 as it fixes some problems with the freebsd build. What's the recommended workflow? Thanks, -- Davide ___ s

Re: [swift-dev] Metadata Representation

> On Sep 22, 2017, at 5:39 PM, Saleem Abdulrasool via swift-dev > wrote: > > Now, as it so happens, both PE and PE+ have limitations on the file size at > 4GiB. This means that we are guaranteed that the relative difference is > guaranteed to fit within 32-bits. This is where things get real

[swift-dev] Thoughts on a hypothetical "Multiple primary file" mode

Hi, all. David Ungar and Graydon Hoare have been doing compiler performance investigations, and in particular are interested in the cases where WMO-with-Onone builds are faster than the multi-file -Onone builds. By now this is out there as a hackaround for build time on targets with many files b

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 16.10 (master) #358

I reverted these commits a while ago. The bots are still catching up. - Doug > On Sep 25, 2017, at 3:43 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-package-linux-ubuntu-16_10 [#358] > > Build URL: > https://ci.swift.org/job/oss-swift-package-linux-ubuntu-16_10/358/ >

Re: [swift-dev] A constraint system / type variable question

> On Sep 25, 2017, at 18:23, Joe Groff wrote: > > > >> On Sep 25, 2017, at 1:04 PM, David Zarzycki wrote: >> >> >> >>> On Sep 25, 2017, at 14:37, Joe Groff wrote: >>> >>> >>> On Sep 23, 2017, at 10:36 PM, Robert Widmann via swift-dev wrote: Why is the arrow carr

Re: [swift-dev] A constraint system / type variable question

> On Sep 25, 2017, at 1:04 PM, David Zarzycki wrote: > > > >> On Sep 25, 2017, at 14:37, Joe Groff wrote: >> >> >> >>> On Sep 23, 2017, at 10:36 PM, Robert Widmann via swift-dev >>> wrote: >>> >>> Why is the arrow carrying the “Has Value Semantics Bit” rather than it >>> being part of

Re: [swift-dev] A constraint system / type variable question

> On Sep 25, 2017, at 14:37, Joe Groff wrote: > > > >> On Sep 23, 2017, at 10:36 PM, Robert Widmann via swift-dev >> wrote: >> >> Why is the arrow carrying the “Has Value Semantics Bit” rather than it being >> part of a protocol composition on an argument type, or a convention bit on >>

[swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #355

Title: Report [FAILURE] oss-swift-package-osx [#355] Build URL:https://ci.swift.org/job/oss-swift-package-osx/355/ Project:oss-swift-package-osx Date of build:Mon, 25 Sep 2017 13:42:26 -0500 Build duration:53 min Identified problems:Compile Error: This build failed becaus

Re: [swift-dev] Metadata Representation

> On Sep 25, 2017, at 12:24 PM, Joe Groff wrote: >> On Sep 24, 2017, at 10:30 PM, John McCall wrote: >>> On Sep 22, 2017, at 8:39 PM, Saleem Abdulrasool >>> wrote: >>> >>> On Thu, Sep 21, 2017 at 10:28 PM, John McCall wrote: >>> On Sep 21, 2017, at 10:10 PM, Saleem Abdulrasool wr

Re: [swift-dev] libdispatch switched to CMake

> On Sep 25, 2017, at 11:28, Jordan Rose wrote: > > > >> On Sep 24, 2017, at 19:32, Saleem Abdulrasool > > wrote: >> >> On Sat, Sep 23, 2017 at 5:02 AM, David P Grove > > wrote: >> With autotools, the first time libdispatch was built (f

Re: [swift-dev] A constraint system / type variable question

> On Sep 23, 2017, at 10:36 PM, Robert Widmann via swift-dev > wrote: > > Why is the arrow carrying the “Has Value Semantics Bit” rather than it being > part of a protocol composition on an argument type, or a convention bit on > the parameter like ‘inout’? Value semantics is a property of

Re: [swift-dev] libdispatch switched to CMake

> On Sep 24, 2017, at 19:32, Saleem Abdulrasool wrote: > > On Sat, Sep 23, 2017 at 5:02 AM, David P Grove > wrote: > With autotools, the first time libdispatch was built (for SourceKit), it just > did the C build of libdispatch. That had to be blown away and rebuilt

Re: [swift-dev] Metadata Representation

> On Sep 25, 2017, at 10:28 AM, Jordan Rose wrote: > > > >> On Sep 25, 2017, at 09:24, Joe Groff via swift-dev > > wrote: >> >> >> >>> On Sep 24, 2017, at 10:30 PM, John McCall >> > wrote: >>> >>> On Sep 22, 2017, at 8:39 PM, Sa

Re: [swift-dev] Metadata Representation

> On Sep 25, 2017, at 1:28 PM, Jordan Rose wrote: >> On Sep 25, 2017, at 09:24, Joe Groff via swift-dev > > wrote: >>> On Sep 24, 2017, at 10:30 PM, John McCall >> > wrote: >>> >>> On Sep 22, 2017, at 8:39 PM, Saleem Abdulrasool >>>

Re: [swift-dev] Metadata Representation

> On Sep 25, 2017, at 09:24, Joe Groff via swift-dev > wrote: > > > >> On Sep 24, 2017, at 10:30 PM, John McCall wrote: >> >> >>> On Sep 22, 2017, at 8:39 PM, Saleem Abdulrasool >>> wrote: >>> >>> On Thu, Sep 21, 2017 at 10:28 PM, John McCall wrote: >>> On Sep 21, 2017, at 10:10

Re: [swift-dev] Metadata Representation

> On Sep 24, 2017, at 10:30 PM, John McCall wrote: > > >> On Sep 22, 2017, at 8:39 PM, Saleem Abdulrasool >> wrote: >> >> On Thu, Sep 21, 2017 at 10:28 PM, John McCall wrote: >> >>> On Sep 21, 2017, at 10:10 PM, Saleem Abdulrasool >>> wrote: >>> >>> On Thu, Sep 21, 2017 at 5:18 PM, Joh

Re: [swift-dev] Function overload resolution

func triple(_ x: Int) -> Int { return 3 * x } extension Int { func triple() -> Int { return triple(self) // Error here } } The error reads: Playground execution failed: > error: Test.playground:5:16: error: use of 'triple' refers to instance > method 'triple()' rather th

Re: [swift-dev] A constraint system / type variable question

Thanks John! I’ll find a workaround or just punt on this QoI work for now. Dave > On Sep 24, 2017, at 23:06, John McCall wrote: > >> On Sep 24, 2017, at 1:13 AM, David Zarzycki via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> Hi Robert, >> >> As a prerequisite to some other hacking I’