Re: [swift-dev] Building Foundation on FreeBSD

> On Dec 19, 2015, at 7:14 , Davide Italiano wrote: > > On Fri, Dec 18, 2015 at 7:58 AM, Davide Italiano > wrote: >> On Wed, Dec 16, 2015 at 2:25 PM, Jordan Rose wrote: >>> On Dec 16, 2015, at 11:21 , Davide Italiano wrote: On Wed, Dec 16, 2015 a

[swift-dev] Cross Compiling Swift for Bare Metal?

Hi, I wanted to know if it is possible to compile swift code for bare metal. I know there is a runtime but does swift depend on it to execute even if I don't use those features?, can I disable them somehow. I was hoping that since you can produce LLVM Bytecode that you can cross compile using

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

Swift: d9802dd59b now builds successfully for me... thanks Dmitri! On Sat, Dec 19, 2015 at 6:52 PM, Dmitri Gribenko wrote: > Thanks everyone for the investigation. I reproduced the issue and found > that this test fails in the AST verifier, so I annotated it as such in > https://github

Re: [swift-dev] C-style For Loops

> > Why? > Because this works: var rangeA = -150.0..<150 for lat in rangeA.by(30) { print(lat) } And this not: var rangeC = -150..<150 for lat in rangeC.by(30) { // Error - Value of type 'Range' has no member 'by' print(lat) } I think this is expected to work, or not? If you make a e

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

Hi Joe, Please ignore the swift-2.2-branch for now. Main development is happening on 'master'. The swift-2.2-branch will be used as the release branch for Swift 2.2. Details will be sent out soon, but right now the branch is in a bring up stage to work with a specific version of Clang. Chee

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

Thanks everyone for the investigation. I reproduced the issue and found that this test fails in the AST verifier, so I annotated it as such in https://github.com/apple/swift/commit/d9802dd59b0e98063ea57aa51435424dc8d304c7 . The buildbot_linux_1404 preset now works for me. Dmitri On Sat, Dec 19,

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

SIL/crashers/004-swift-expr-getsourcerangle.sil continues to fail with a clean checkout and using the buildbot_linux to compile everything. Clang: f66c5bb67b LLVM: 3ebdbb2c7e Swift: 696544a000 Foundation: d9817a41ae Everything else is clean, to work around it for now I

Re: [swift-dev] C-style For Loops

> I personally liked the original free-function syntax—"stride(from: -50, to: > 50, by: 9)". When we got protocol extensions, we decided we'd prefer methods > everywhere except in a few special cases, and this clearly falls outside > those criteria. I don't know about that—in `stride(from: -50

Re: [swift-dev] Dockerized Swift, Build Times and Other Notes Regarding CI

Thanks! The non-prebuilts work well. It took a while for me to work out the details. The 14.04 prebuilt container is having some issues which is why it's still private on Hub. I can make it public or add you to it. I must be missing something in mimicking the buildbot_linux preset minus tests, bec

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

Related to this, what branch should one actually be building if they are hoping to create a version that looks like the 2.2-SNAPSHOT. There is a master branch and a swift-2.2-branch in the repo, with the default git clone branch being master. What purpose does the swift-2.2-branch server? Also,

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

Thanks Emanuel, I was operating with a clean environment and see another dependency has been added to the buildbot_linux (swift-integration-tests) so I'll pull that down and build again. On Sat, Dec 19, 2015 at 4:54 PM, Emanuel Zephir wrote: > I can't reproduce this on Ubuntu 14.04 or on OS X

Re: [swift-dev] C-style For Loops

> On Dec 19, 2015, at 2:24 PM, Brent Royal-Gordon > wrote: > >>> One practical reason is that interval.start must always be before >>> interval.end, so this makes striding in reverse difficult. >> >> We could declare that negative strides cause us to start at the end rather >> than at the st

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

I can't reproduce this on Ubuntu 14.04 or on OS X 10.10 at 696544a0. On Linux: Expected Passes: 6964 Expected Failures : 100 Unsupported Tests : 622 -- check-swift-all-linux-x86_64 finished -- --- Finished tests for swift --- Specifically on the SIL Crashers, the results are: PASS:

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

That is interesting, this was on Ubuntu 15.10, the other being on 14.04: Testing Time: 260.04s Failing Tests (1): Swift :: SIL/crashers/004-swift-expr-getsourcerange.sil Expected Passes: 6965 Expected Failures : 100 Unsupported Tests : 620

Re: [swift-dev] C-style For Loops

>> One practical reason is that interval.start must always be before >> interval.end, so this makes striding in reverse difficult. > > We could declare that negative strides cause us to start at the end rather > than at the start. I've noticed in the past that the Swift standard library does no

Re: [swift-dev] C-style For Loops

> On Dec 19, 2015, at 1:47 PM, Brent Royal-Gordon > wrote: > >>> for lat in (CGFloat(-60)...60).by(30) { >>> print(lat) >>> } >>> >>> for lat in (CGFloat(-60)..<60).by(30) { >>> print(lat) >>> } >> >> This is nice; why don't we put it in the standard library and get rid of the >> "stride"

Re: [swift-dev] C-style For Loops

> On Dec 19, 2015, at 1:20 PM, Wallacy wrote: > > Curiously I was analyzing this part of the library a few minutes ago. > It will probably be necessary to extend "Range": > > extension Range where Element: Strideable { > func by(n: Element.Stride) -> StrideThrough { > return startIn

Re: [swift-dev] C-style For Loops

>> for lat in (CGFloat(-60)...60).by(30) { >> print(lat) >> } >> >> for lat in (CGFloat(-60)..<60).by(30) { >> print(lat) >> } > > This is nice; why don't we put it in the standard library and get rid of the > "stride" methods? One practical reason is that interval.start must always be befo

Re: [swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

Last commit: 696544a0003d43de824ead0b4ec9c19fda9a7553 (4 hours ago) Testing Time: 1838.83s Expected Passes: 2357 Expected Failures : 5 Unsupported Tests : 35 -- check-swift-macosx-x86_64 finished -- --- Finished tests for swift --- Em sáb, 19 de dez de 2015 às 16:47, Joseph Bell via

Re: [swift-dev] C-style For Loops

Curiously I was analyzing this part of the library a few minutes ago. It will probably be necessary to extend "Range": extension Range where Element: Strideable { func by(n: Element.Stride) -> StrideThrough { return startIndex.stride(through: endIndex, by: n) } } The first thing t

Re: [swift-dev] C-style For Loops

> On Dec 19, 2015, at 11:44 AM, Donnacha Oisín Kidney via swift-dev > wrote: > > You can define an extension on interval types: > > extension HalfOpenInterval where Bound: Strideable { > func by(n: Bound.Stride) -> StrideTo { > return start.stride(to: end, by: n) > } > } > > extension

[swift-dev] Including third-party code in repo

Hello, I'm currently working on a port of Swift to Android. Since Android's libc is missing a few required methods, I added code from a few other sources to implement the functionality. Specifically, I added an implementation of posix_spawn from the FreeBSD libc, floating point routines from A

Re: [swift-dev] Dockerized Swift, Build Times and Other Notes Regarding CI

This is great! On that note I think I will change the swiftdocker/swift-dev container to offer just a development dependency environment, in favour of the work you’re doing there for prebuilt stuff, and I’ll make a repo building off of what you’ve done there with different environments for a qui

Re: [swift-dev] C-style For Loops

You can define an extension on interval types: extension HalfOpenInterval where Bound: Strideable { func by(n: Bound.Stride) -> StrideTo { return start.stride(to: end, by: n) } } extension ClosedInterval where Bound: Strideable { func by(n: Bound.Stride) -> StrideThrough { return st

Re: [swift-dev] Dockerized Swift, Build Times and Other Notes Regarding CI

Hi Tom/Max, I've made a dockerized Swift build using the build_bot preset for Ubuntu 14/15 and Fedora: https://github.com/eosrei/docker-swift-dev-buildbot and https://hub.docker.com/r/eosrei/swift-dev-buildbot/ The three containers could be used right now for CI. There is some work on a "preheate

[swift-dev] C-style For Loops

With C-style for loops to be removed from the language to general acclaim (including mine), is the following the best way to perform the required looping: for lat in (CGFloat(-60.0)).stride(through: +60.0, by: 30.0) { path.moveToPoint(CGPointMake(-180.0, lat)) path.lineToPoint

[swift-dev] SIL/crashes/004-swift-expr-getsourcerange.sil

Can anyone confirm or deny that this is a known issue at the moment? This is with a fresh checkout as of this morning (Dec 19). Testing Time: 261.00s Failing Tests (1): Swift :: SIL/crashers/004-swift-expr-getsourcerange.sil Expected Passes: 69

Re: [swift-dev] Building Foundation on FreeBSD

On Fri, Dec 18, 2015 at 7:58 AM, Davide Italiano wrote: > On Wed, Dec 16, 2015 at 2:25 PM, Jordan Rose wrote: >> >>> On Dec 16, 2015, at 11:21 , Davide Italiano wrote: >>> >>> On Wed, Dec 16, 2015 at 11:17 AM, Jordan Rose wrote: What's the compile command for the files that are failing? If

[swift-dev] New Swift 2.2 Toolchain snapshot - Dec 18, 2015

New Swift 2.2 snapshot available! Download new packages from https://swift.org/download/ Following repository are tagged with swift-2.2-SNAPSHOT-2015-12-18-a https://github.com/apple/swift https://