Re: [swift-dev] [Compiler] Help IR gen in targetting MSVC

> On Apr 25, 2016, at 7:54 PM, Sangjin Han via swift-dev > wrote: > Hi all, > > I found a bug in my port for MSVC and Cygwin. > > The C function swift_stdlib_readLine_stdin() is mapped to 'Int' type in > Swift, but it generates i32 in LLVM if I specify the target as MSVC. If I > give the targ

[swift-dev] New Swift snapshots available!

New Swift snapshots available! Download new packages from https://swift.org/download/ Swift 2.2.x: (swift-2.2-branch) Following repository are tagged with swift-2.2.1-SNAPSHOT-2016-04-23-a https://github.com/apple/swift

Re: [swift-dev] Swift incremental compile profiling

> On Apr 25, 2016, at 8:15 PM, Samantha John wrote: > > On Mon, Apr 25, 2016 at 12:11 AM, Daniel Dunbar > wrote: > >> On Apr 24, 2016, at 3:19 PM, Samantha John via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> Hello List (cc/Jordan), >> >> At a hi

Re: [swift-dev] Swift incremental compile profiling

On Mon, Apr 25, 2016 at 12:11 AM, Daniel Dunbar wrote: > > On Apr 24, 2016, at 3:19 PM, Samantha John via swift-dev < > swift-dev@swift.org> wrote: > > Hello List (cc/Jordan), > > At a high level: Brian and I are looking into contributing to incremental > compilation in Swift. Right now we're try

[swift-dev] [Compiler] Help IR gen in targetting MSVC

Hi all, I found a bug in my port for MSVC and Cygwin. The C function swift_stdlib_readLine_stdin() is mapped to 'Int' type in Swift, but it generates i32 in LLVM if I specify the target as MSVC. If I give the target as Cygwin, it generates i64. With the target options, the Cygwin ported swiftc.e

Re: [swift-dev] ASan runtime does not come first

Indeed the install location proves to be the root issue. When LLDB is installed in /usr/bin/lldb we also wind up with content under /usr/lib/lldb that are presumed to be plugins – even though they aren't. When an ASAN enabled library is loaded to initialize the plugin it notices LLDB isn't ru

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

Hi Daniel, Job updated to checkout swift-package-manager. Thanks, Mishal Shah > On Apr 25, 2016, at 4:52 PM, Daniel Dunbar wrote: > > Mishal, I believe this failed because this builder doesn't have the swiftpm > source checked out, even though it does for Linux (and the @swift-ci test > bui

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

Mishal, I believe this failed because this builder doesn't have the swiftpm source checked out, even though it does for Linux (and the @swift-ci test builders do, apparently). Can you update the Jenkins config to also checkout out the OSS apple/swift-package-manager? I will revert in the meanti

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

Obj-C only test; fixed now. - Doug > On Apr 25, 2016, at 4:18 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#4500] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4500/ >

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

> On Apr 25, 2016, at 3:30 PM, Jordan Rose wrote: > >> I, personally, *really* don’t want yet another decorator keyword to indicate >> the intent here, because I believe the user has already indicated intent by >> stating conformance to the protocol P. > > I don't find this so compelling in a

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

> I, personally, *really* don’t want yet another decorator keyword to indicate > the intent here, because I believe the user has already indicated intent by > stating conformance to the protocol P. I don't find this so compelling in a language with defaulted requirements. The place where we're

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

> On Apr 25, 2016, at 10:09 AM, John McCall wrote: > >> On Apr 25, 2016, at 9:57 AM, Douglas Gregor > > wrote: >>> On Apr 22, 2016, at 6:08 PM, John McCall >> > wrote: >>> On Apr 22, 2016, at 3:33 PM, Douglas Gregor via swift-dev m

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

> On Apr 25, 2016, at 10:09 AM, John McCall via swift-dev > wrote: > >> On Apr 25, 2016, at 9:57 AM, Douglas Gregor > > wrote: >>> On Apr 22, 2016, at 6:08 PM, John McCall >> > wrote: >>> On Apr 22, 2016, at 3:33 PM, Douglas Gregor via s

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

> On Apr 25, 2016, at 10:12 AM, Douglas Gregor wrote: >> On Apr 25, 2016, at 10:09 AM, John McCall > > wrote: >> >>> On Apr 25, 2016, at 9:57 AM, Douglas Gregor >> > wrote: On Apr 22, 2016, at 6:08 PM, John McCall >>>

Re: [swift-dev] Libraries written in Objective-C in Swift 3

Hi Chris, > On Apr 25, 2016, at 5:45 AM, Chris Bailey via swift-dev > wrote: > > Is there a view (yet) on if/when/how the "Swift" implementation of Foundation > will be used on Darwin? > > Currently under TestFoundation, the "Swift" version is its imported as > SwiftFoundation on Darwin. Is

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

> On Apr 25, 2016, at 9:57 AM, Douglas Gregor wrote: >> On Apr 22, 2016, at 6:08 PM, John McCall > > wrote: >> >>> On Apr 22, 2016, at 3:33 PM, Douglas Gregor via swift-dev >>> mailto:swift-dev@swift.org>> wrote: >>> Hi all, >>> >>> A common complaint with protocol co

Re: [swift-dev] ASan runtime does not come first

What I've found out so far is that the tree built in the 'install' directory (./install/usr) is not suitable to live side-by-side with /usr/ on the host machine. My original approach (documented on http://dev.iachieved.it/iachievedit/) was to ball everything up into a .deb package that installed a

[swift-dev] TWISt-shout Newsletter 2016-04-25

Here is your TWISt-shout newsletter for the week of 2016-04-18 to 2016-04-24 https://github.com/pepperdog/TWISt-shout/blob/master/2016/TWISt-shout-2016-04-25.md Enjoy! -Kenny ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailm

Re: [swift-dev] RFC: "Near-miss" checking for defaulted protocol requirements

> On Apr 22, 2016, at 6:08 PM, John McCall wrote: > >> On Apr 22, 2016, at 3:33 PM, Douglas Gregor via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> Hi all, >> >> A common complaint with protocol conformance checking is that it’s easy to >> make a little mistake when trying to implement

Re: [swift-dev] ASan runtime does not come first

I've just noticed (thanks to you Ryan) that compiler-rt is indeed checked out and included in the 14.04 build but not the 15.10. I'm going to rebuild from the ground up on 15.10 to see if it grabs compiler-rt and reproduces, as this is being checked out by the ci.swift.org CI server. This error o

Re: [swift-dev] build error: INSTALL cannot find readline.so

Rob, this is a known build bug tracked by https://bugs.swift.org/browse/SR-1287. I have only been able to reproduce this by restarting a build after some previous failure. The workaround (for me at least) is to delete the build directory and restart from the beginning (not ideal to be sure). Joe

Re: [swift-dev] ASan runtime does not come first

On Sun, Apr 24, 2016, at 05:44 PM, Joseph Bell via swift-dev wrote: > Well, I thought the REPL issues had all been put to rest, but now I am > seeing this on Ubuntu 14.04 (15.10 I do not see it): > > ➜  package-swift-3.0 git:(swift-3.0) ✗ ./install/usr/bin/swift > ==18928==ASan runtime does not com

Re: [swift-dev] Libraries written in Objective-C in Swift 3

Is there a view (yet) on if/when/how the "Swift" implementation of Foundation will be used on Darwin? Currently under TestFoundation, the "Swift" version is its imported as SwiftFoundation on Darwin. Is the medium/long term view? ie, that the Swift implementation will be "SwiftFoundation", with

[swift-dev] build error: INSTALL cannot find readline.so

Hi, I'm trying to compile swift manually using this command: swift/utils/build-script --preset=buildbot_linux_1510 installable_package=/home/rob/swift.tar.gz install_destdir=/home/rob/swift-install It all seems to go okay until this error: Make Error at scripts/Python/modules/readline/cmake_