[swift-dev] Adding a CHECK to test case.

Hi, clang_inline_opt.swift test case is failing on ppc64le with following error: /root/swift-source/swift/test/IRGen/clang_inline_opt.swift:10:11: error: expected string not found in input // CHECK: define internal i32 @return7() [[CLANG_ATTRS:#[0-9]+]] { ^ :1:1: note: scanning from

[swift-dev] Make offset index available for String

Hi, I would like to discuss the String.Index problem within Swift. I know the current situation of String.Index is based on the nature of the underlaying data structure of the string. But could we just make String.Index contain offset information? Or make offset index subscript available for

Re: [swift-dev] Preserving and Applying CC in Imported Decls

> On Dec 13, 2017, at 8:35 PM, Saleem Abdulrasool wrote: > > On Wed, Dec 13, 2017 at 4:14 PM, John McCall > wrote: > >> On Dec 13, 2017, at 6:42 PM, Saleem Abdulrasool >

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #916

Arnold, these backtraces imply that it’s your change. Sent from my iPhone > On Dec 13, 2017, at 9:54 PM, swift...@swift.org wrote: > > [FAILURE] swift-master-source-compat-suite [#916] > > Build URL:https://ci.swift.org/job/swift-master-source-compat-suite/916/ > Project:

Re: [swift-dev] Preserving and Applying CC in Imported Decls

On Wed, Dec 13, 2017 at 4:14 PM, John McCall wrote: > > On Dec 13, 2017, at 6:42 PM, Saleem Abdulrasool > wrote: > > > > On Dec 13, 2017, at 12:46 PM, John McCall wrote: > > > On Dec 13, 2017, at 3:22 PM, Saleem Abdulrasool

Re: [swift-dev] Preserving and Applying CC in Imported Decls

> On Dec 13, 2017, at 6:42 PM, Saleem Abdulrasool wrote: > > > >> On Dec 13, 2017, at 12:46 PM, John McCall > > wrote: >> >>> >>> On Dec 13, 2017, at 3:22 PM, Saleem Abdulrasool >>

Re: [swift-dev] Preserving and Applying CC in Imported Decls

> On Dec 13, 2017, at 12:46 PM, John McCall wrote: > >> >> On Dec 13, 2017, at 3:22 PM, Saleem Abdulrasool > > wrote: >> >> >> >>> On Dec 13, 2017, at 12:14 PM, John McCall >>

Re: [swift-dev] Protocol Devirtualizer Pass

You don’t need a second open_existential_ref in the _wrap_inc function. It should look something like this: sil @_wrap_inc : $@convention(thin) (@owned T, Int) -> Int { bb0(%0 : $T, %1 : $Int): %5 = witness_method $T, #SumProtocol.inc!1 : (Self) -> (Int) -> Int :

Re: [swift-lldb-dev] [swift-dev] Switching swift to C++14

FWIW, llbuild requires C++14. We have to do some minor shenanigans to workaround bugs in libstdc++ on 14.04, and our use is probably minimal, but just throwing that out there. - Daniel > On Dec 13, 2017, at 1:45 PM, Jordan Rose via swift-lldb-dev > wrote: > > No

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

FWIW, llbuild requires C++14. We have to do some minor shenanigans to workaround bugs in libstdc++ on 14.04, and our use is probably minimal, but just throwing that out there. - Daniel > On Dec 13, 2017, at 1:45 PM, Jordan Rose via swift-lldb-dev > wrote: > > No

Re: [swift-dev] Switching swift to C++14

> On Dec 13, 2017, at 2:30 PM, Jordan Rose wrote: > > > >> On Dec 13, 2017, at 14:19, Saleem Abdulrasool wrote: >> >>> On Dec 13, 2017, at 1:45 PM, Jordan Rose wrote: >>> >>> No one else has commented on this yet today,

Re: [swift-lldb-dev] [swift-dev] Switching swift to C++14

> On Dec 13, 2017, at 14:19, Saleem Abdulrasool wrote: > >> On Dec 13, 2017, at 1:45 PM, Jordan Rose wrote: >> >> No one else has commented on this yet today, so I'll put in that I don't >> have any objections to this and don't foresee any major

Re: [swift-dev] Switching swift to C++14

> On Dec 13, 2017, at 14:19, Saleem Abdulrasool wrote: > >> On Dec 13, 2017, at 1:45 PM, Jordan Rose wrote: >> >> No one else has commented on this yet today, so I'll put in that I don't >> have any objections to this and don't foresee any major

Re: [swift-dev] Switching swift to C++14

> On Dec 13, 2017, at 1:45 PM, Jordan Rose wrote: > > No one else has commented on this yet today, so I'll put in that I don't have > any objections to this and don't foresee any major problems. The one place > where we'd need to be careful is with LLDB, which imports

Re: [swift-dev] Switching swift to C++14

No one else has commented on this yet today, so I'll put in that I don't have any objections to this and don't foresee any major problems. The one place where we'd need to be careful is with LLDB, which imports Swift headers; if Swift is going to move to C++14, then Swift-LLDB probably has to

Re: [swift-lldb-dev] [swift-dev] Switching swift to C++14

No one else has commented on this yet today, so I'll put in that I don't have any objections to this and don't foresee any major problems. The one place where we'd need to be careful is with LLDB, which imports Swift headers; if Swift is going to move to C++14, then Swift-LLDB probably has to

Re: [swift-dev] Protocol Devirtualizer Pass

Slava, I have two (clarification) questions in your proposed implementation: *Original Function:* @inline(never) internal func wrap_inc(a:SumProtocol, val:Int) -> Int{ return a.increment(i:val) } *Transformed code:* @inline(always) internal func wrap_inc(a: SumProtocol, val: Int) -> Int { //

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 16.04 (swift 4.1) #336

Fixed > On Dec 13, 2017, at 8:24 AM, David Hart wrote: > > mkdir: cannot create directory > `/www-data/tmp-builds/swift-4.1-DEVELOPMENT-SNAPSHOT-2017-12-13-a-338': No > space left on device > >  > >> On 13 Dec 2017, at 17:22, swift...@swift.org

Re: [swift-dev] Disk full ---> Re: [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #840

Fixed. > On Dec 13, 2017, at 9:50 AM, David Zarzycki via swift-dev > wrote: > > > > >> On Dec 13, 2017, at 11:34, swift-ci--- via swift-dev > > wrote: >> >> [FAILURE] oss-swift-package-osx [#840] >> >> Build URL:

[swift-dev] Switching swift to C++14

Hi, The newer Windows SDK requires the use of C++14 (the SDK headers use `auto` return types without trailing type information). Joe mentioned that there was some interest in switching the rest of swift to C++14 as well. I figured that I would just start a thread here to determine if this is

[swift-dev] Disk full ---> Re: [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #840

> On Dec 13, 2017, at 11:34, swift-ci--- via swift-dev > wrote: > > [FAILURE] oss-swift-package-osx [#840] > > Build URL:https://ci.swift.org/job/oss-swift-package-osx/840/ > > Project:

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

Title: Report [FAILURE] oss-swift-4.1-package-osx [#336] Build URL:https://ci.swift.org/job/oss-swift-4.1-package-osx/336/ Project:oss-swift-4.1-package-osx Date of build:Wed, 13 Dec 2017 06:30:29 -0600 Build duration:2 hr 44 min Changes No

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

Title: Report [FAILURE] oss-swift-package-osx [#840] Build URL:https://ci.swift.org/job/oss-swift-package-osx/840/ Project:oss-swift-package-osx Date of build:Wed, 13 Dec 2017 06:31:03 -0600 Build duration:2 hr 44 min Changes No Changes

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 16.04 (swift 4.1) #336

mkdir: cannot create directory `/www-data/tmp-builds/swift-4.1-DEVELOPMENT-SNAPSHOT-2017-12-13-a-338': No space left on device  > On 13 Dec 2017, at 17:22, swift...@swift.org wrote: > > [FAILURE] oss-swift-4.1-package-linux-ubuntu-16_04 [#336] > > Build URL: >

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

This seems unrelated to my commit as its a CLF test that is failing: TestURLSession.test_simpleUploadWithDelegate : XCTAssertEqual failed: ("0") is not equal to ("16384") - > On 13 Dec 2017, at 16:25, swift...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-16_10 [#1980]