[swift-dev] Starter project: Port Swift to RHEL 7 / CentOS 7 / Scientific Linux 7

Hi, RHEL 7 and CentOS 7 are widely used as server operating systems, and porting Swift to these distributions would benefit many community members. It should be relatively easy to do, since RHEL 7 is fundamentally another Linux system that uses the same basic libraries as other Linux ports we

Re: [swift-dev] Verify failed

On Sun, Dec 6, 2015 at 9:08 AM, Piero Sabino via swift-dev wrote: > Yes, I've downloaded signature file and swift in the same directory. Could you post the actual error message, and SHA1 hashes of the files? Dmitri --

Re: [swift-dev] Starter project: Port Swift to RHEL 7 / CentOS 7 / Scientific Linux 7

On Mon, Dec 7, 2015 at 10:25 AM, Meador Inge <mead...@gmail.com> wrote: > On Mon, Dec 7, 2015 at 11:47 AM, Dmitri Gribenko via swift-dev > <swift-dev@swift.org> wrote: > >> Hi, >> >> RHEL 7 and CentOS 7 are widely used as server operating systems, and >&g

Re: [swift-dev] [SR-40] Port Swift to Arm progress / question

Here's a relevant line (there are lots, this is just one instance): 003a91cc 0015d403 R_ARM_REL32 003af914 _TMps13GeneratorType _TMps13GeneratorType ---> protocol descriptor for Swift.GeneratorType Dmitri On Wed, Dec 9, 2015 at 7:25 PM, William Dillon wrote:

Re: [swift-dev] Porting swift to FreeBSD

On Sun, Dec 13, 2015 at 2:52 AM, Davide Italiano wrote: > And now, swift compiled programs run correctly on FreeBSD! This is great, thanks Davide! > % ./swiftc hello.swift -o hello > davide@rabbit1:/exps/swift/build/Ninja-ReleaseAssert/swift-freebsd-x86_64/bin > % ./hello

Re: [swift-dev] Porting swift to FreeBSD

On Sat, Dec 12, 2015 at 9:26 PM, Davide Italiano wrote: > On Sun, Dec 13, 2015 at 12:22 AM, Dmitri Gribenko wrote: >> On Sat, Dec 12, 2015 at 9:09 PM, Davide Italiano >> wrote: >>> On Sat, Dec 12, 2015 at 11:45 PM, Dmitri

[swift-dev] Starter project: increase test coverage on Linux

Hi, Many important tests are XFAIL'ed on Linux. Usually this is because one or few parts of the test use the Objective-C runtime or rely on Foundation. These parts can usually be separated into separate files, or guarded with `#if _runtime(_ObjC)`. Sometimes these failures are real issues that

Re: [swift-dev] buildbot configuration + etc

+Mishal Awadah, Mishal Shah On Mon, Dec 14, 2015 at 8:04 PM, Travis Tilley via swift-dev < swift-dev@swift.org> wrote: > Is there any documentation somewhere on what the exact commands are that > the buildbot CI performs and how the packages on swift.org are created? > > I've noticed that: > >

Re: [swift-dev] [SR-40] Port Swift to Arm progress / question

On Mon, Dec 14, 2015 at 11:20 PM, William Dillon wrote: > I built a very simple swift program (minimal hello world) using the arm > swiftc and the x86_64 swiftc, and had them emit the sil and llvm ir. The sil > it substantially similar between the toolchain tarball on

[swift-dev] Starter project: add stable sort to the standard library

Hi, The standard library should provide a stable sort. This needs a proposal to swift-evolution (the design should be trivial, new methods should mirror existing sorting APIs), and implementation. The standard library already contains an internal implementation of insertion sort, so

Re: [swift-dev] Starter project: SR-2: Build configuration directives can not wrap switch cases

On Thu, Dec 17, 2015 at 7:58 AM, Meador Inge <mead...@gmail.com> wrote: > On Sun, Dec 6, 2015 at 5:04 PM, Dmitri Gribenko via swift-dev > <swift-dev@swift.org> wrote: > >> Hi, >> >> If you're looking for a starter project in the frontend area (parser >

Re: [swift-dev] Combining Skin Tone Emoji Into Single Extended Grapheme Clusters

Hi Michael, On Thu, Dec 17, 2015 at 9:16 PM, Michael Buckley via swift-dev < swift-dev@swift.org> wrote: > Hello, > > I would like to fix rdar://20511834 , which is that the new skin tone and > multi-person grouping emoji introduced with iOS 8.3 and OS X 10.10.3 are > represented as multiple

Re: [swift-dev] preset: buildbot_linux_1404/1510 are the same

On Thu, Dec 10, 2015 at 10:33 AM, Brad Erickson via swift-dev wrote: > > The best solution is to remove one and rename the other simply: [preset: > buildbot_linux], but that will have far reaching effects. Nothing that can't > be dealt with though. How should this be

Re: [swift-dev] Beginner's questions about building Swift from source etc.

Mish Awadah probably knows about setting up a custom toolchain in Xcode. Dmitri On Thu, Dec 10, 2015 at 9:44 PM, Jens Persson wrote: > Thanks again, > I pulled the latest Swift repos which included the fix of the failing test > and modified the build preset locally according

Re: [swift-dev] Running only one unit test through build-script?

On Sun, Dec 13, 2015 at 10:34 PM, Austin Zheng via swift-dev wrote: > Apologies if I'm overlooking something basic. I looked through the help for > both build-script and build-script-impl, and while I found flags to disable > parts of the prebuilt test suites, it doesn't

Re: [swift-dev] Porting Swift to Linux aarch64 (arm64)

On Mon, Dec 14, 2015 at 3:16 PM, William Dillon wrote: > Thanks Dmitri, > > I’ve been reading cmake files all day, and noticing that some references to > the gold linker (specifically this one in cmake/modules/AddSwift): > > 1058 # Handle gold linker flags for shared

Re: [swift-dev] Current master is failing on 3 tests

+Nadav who committed these tests in 25832d39b22eb30370e7f1dc855e4919590f528f. On Thu, Dec 31, 2015 at 8:51 PM, Kevin Ballard via swift-dev wrote: > Running tests on current master fails on 3 tests every time. I already > checked to make sure I'm fully up-to-date. They

Re: [swift-dev] Should we remove _customContainsEquatableElement from stdlib?

On Wed, Dec 30, 2015 at 8:34 PM, Ling Wang via swift-dev wrote: > After reviewing the code of stdlib I found no one actually implements > _customContainsEquatableElement: > 1. Its default implementation in `SequenceType` just returns nil. > 2. The implementation in `Set`

Re: [swift-dev] Reducing the size of Swift binaries by shortening symbols

On Sun, Dec 20, 2015 at 9:43 PM, Nadav Rotem wrote: > > On Dec 20, 2015, at 2:17 AM, Dmitri Gribenko wrote: > > + Stephen Canon, because he probably has good ideas in this domain. > > On Fri, Dec 18, 2015 at 3:42 PM, Nadav Rotem via swift-dev >

Re: [swift-dev] Reducing the size of Swift binaries by shortening symbols

+ Stephen Canon, because he probably has good ideas in this domain. On Fri, Dec 18, 2015 at 3:42 PM, Nadav Rotem via swift-dev < swift-dev@swift.org> wrote: > > *What’s next?* > > The small experiment I described above showed that compressing the names > in the string table has a huge potential

Re: [swift-dev] [swift-corelibs-dev] Defining _GNU_SOURCE for module-map-included headers

+ swift-dev, Jordan On Sun, Dec 20, 2015 at 2:21 AM, Dan Stenmark via swift-corelibs-dev wrote: > I'm trying to invoke Linux's unshare() system call from Swift, but without > much success. From C, it requires _GNU_SOURCE to be #define'd before the > #include .

Re: [swift-dev] operator overloads

On Thu, Dec 17, 2015 at 11:20 AM, Rafkind, Jon via swift-dev wrote: > How does the Swift compiler determine which method or operator to call given > a set of overloads at a given call site? This question may conflate two > issues: method overloads and operator overloads,

Re: [swift-dev] Please remove your Swift build directory

On Wed, Jun 1, 2016 at 12:36 PM, Austin Zheng wrote: > Hello, > > I'm still seeing errors when I try invoking the build script with `-x`. I've > updated all the repositories (everything that lives alongside the 'swift' > repo, as well as that repo itself) and deleted my

Re: [swift-dev] need help with GLibc module map problem

On Thu, Jun 2, 2016 at 2:58 PM, David P Grove via swift-dev wrote: > As part of helping to resolve old libdispatch pull requests, I have run into > a problem with the GLibc module map on Linux that I need help understanding > and fixing. > > The symptom I am trying to resolve

Re: [swift-dev] need help with GLibc module map problem

On Fri, Jun 3, 2016 at 8:23 AM, David P Grove wrote: > Dmitri Gribenko wrote on 06/02/2016 06:19:33 PM: >> >> Could you check if there are multiple definitions of off_t or mode_t >> in different headers guarded by macros? Something like this, >>

Re: [swift-dev] Delaying the enforcement of ".self" out of Swift 3?

On Thu, Jun 2, 2016 at 2:08 PM, Daniel Dunbar via swift-dev wrote: > As just a user of the language, as much as I hate churn I personally wouldn't > mind seeing this fixed. In this case, I think the laxness can make it harder > for developers to form the right mental model

[swift-dev] Please remove your Swift build directory

Hi, We have merged a CMake and build-script refactoring that requires a from-scratch build. Trying to use an existing build directory will result in strange errors in the middle of the build. Excuse me for the inconvenience. Dmitri --

Re: [swift-dev] Please remove your Swift build directory

On Tue, May 31, 2016 at 10:20 AM, Joe Groff <jgr...@apple.com> wrote: > >> On May 31, 2016, at 9:37 AM, Dmitri Gribenko via swift-dev >> <swift-dev@swift.org> wrote: >> >> Hi, >> >> We have merged a CMake and build-script refactoring th

Re: [swift-dev] Please remove your Swift build directory

On Wed, Jun 1, 2016 at 7:17 AM, Karl via swift-dev wrote: > We’d configure it like this: > - SWIFT_HOST_TRIPLE (e.g x86_64-unknown-linux-gnu) > - SWIFT_DEPLOYMENT_TARGETS (e.g. x86_64-unknown-linux-gnu + > armv7-linux-gnueabihf + armv7-none-linux-androideabi + >

Re: [swift-dev] Standard shared libraries with executable stack

Thank you! I merged your PR, it should be included in the next snapshot. Dmitri On Fri, Jun 17, 2016 at 2:26 PM, Sangjin Han wrote: > Please review the PR #3053. > > 2016-06-18 0:17 GMT+09:00 Dmitri Gribenko : >> >> On Fri, Jun 17, 2016 at 7:31 AM,

Re: [swift-dev] Standard shared libraries with executable stack

On Thu, Jun 16, 2016 at 5:17 AM, Jongsu Kim wrote: > Hi, > >> This could have been caused by our switch from the BFD linker to gold. >> Could you try linking a hello world program using gold linker and >> running it in WSL? > > > I tried to build Swift by not using -fuse-gold

Re: [swift-dev] Standard shared libraries with executable stack

On Fri, Jun 17, 2016 at 7:31 AM, Sangjin Han wrote: > Hi, > > When linking libswiftCore.so, gold linker with --warn-execstack option > generates following messages. > /usr/bin/ld.gold: warning: lib/swift/linux/x86_64/swift_begin.o: missing > .note.GNU-stack section implies

Re: [swift-dev] Ubuntu 14.04 Swift master build failure

+ Michael, who has been working on CMake changes. On Sat, Jun 25, 2016 at 10:14 AM, Joseph Bell via swift-dev wrote: > Confirmed that I can reproduce this on my system (x86_64 Ubuntu14.04) : > build 1585 failed >

Re: [swift-dev] swift --version output changed

+ Michael, who has been working on CMake changes. On Sat, Jun 25, 2016 at 2:48 PM, Joseph Bell via swift-dev wrote: > Howdy, > > I noticed in a build today that the output of swift --version has changed. > Today's build: > > swift --version > Swift version 3.0-dev > Target:

Re: [swift-dev] Standard shared libraries with executable stack

Hi, While there wight be an issue in WSL with executable stacks, Swift does not really need one. If the binary is actually asking for one, it would be great if we could figure out a way to ask the gold linker to not mark stacks as executable. Dmitri On Thu, Jun 16, 2016 at 11:39 PM, Sangjin

Re: [swift-dev] Build Error: Relocation R_X86_64_PC32

On Mon, Mar 14, 2016 at 3:38 PM, Ryan Lovelett wrote: > On Tue, Mar 1, 2016, at 12:16 AM, Dmitri Gribenko wrote: >> IIRC there is no issue in the bug tracker, please feel free to file one! >> >> Also, if you are familiar with binutils internals, it might be helpful >>

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

Looks like it was https://github.com/apple/swift-corelibs-foundation/pull/286 Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j*/ ___ swift-dev mailing list

Re: [swift-dev] quick, spot the UB in this code:

On Wed, Apr 6, 2016 at 9:16 PM, Drew Crawford via swift-dev wrote: > and it should crash > deterministically if it gets non-terminated bytes, or It can't, how would you check for this, only given a pointer? > 2. It should not require null-terminated bytes This operation

Re: [swift-dev] quick, spot the UB in this code:

On Wed, Apr 6, 2016 at 10:03 PM, Drew Crawford wrote: > > On Apr 6, 2016, at 11:51 PM, Dmitri Gribenko wrote: > > This operation converts a C string to a Swift string, so (2) is a > non-starter. > > > Then it is inappropriately named. The name of

Re: [swift-dev] What's the best way to handle failing SourceKit tests?

+Argyrios On Mon, Apr 11, 2016 at 7:55 PM, Michael Buckley via swift-dev wrote: > Hi, > > I'm currently working on SR-1115, adding initializers to Int and Uint to > convert from UnsafePointer, and after making my changes, the > SourceKit/DocSupport/doc_swift_module.swift

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

On Mon, Apr 11, 2016 at 11:07 AM, Dave Abrahams wrote: > > on Sun Apr 10 2016, Austin Zheng wrote: > >> I'm really sorry for dropping the ball and disappearing off the list. I'd >> like >> to help out if I can. I'll check out the current branch tomorrow and see what >> the

Re: [swift-dev] SR-122 / CollectionsMoveIndices.swift Prototype

On Mon, Apr 11, 2016 at 3:16 PM, Dave Abrahams wrote: > > on Mon Apr 11 2016, Shawn Erickson wrote: > >> On Mon, Apr 11, 2016 at 11:42 AM Dave Abrahams wrote: >> >> on Mon Apr 11 2016, Shawn Erickson wrote: >> >> > Anything to attempt on

Re: [swift-dev] Error with SwiftGlibs building for arm-linux

Then you should have a module map for Glibc in the build products. Dmitri On Thu, Mar 24, 2016 at 2:32 PM, Труб Илья wrote: > I have built all targets for arm (including modules and libraries) within the > native arm environment on arm-emulator with chroot. > > 25.03.2016,

Re: [swift-dev] Error with SwiftGlibs building for arm-linux

On Thu, Mar 24, 2016 at 1:30 PM, Труб Илья wrote: > Dear colleagues > I have faced with strange behaviour, when I compile some swift source on > Ubuntu 14, target=arm-linux-gnueabi, all neccessary modules for arm present, > -sysroot and > -isysroot are passed via -Xcc. > >

Re: [swift-dev] Error with SwiftGlibs building for arm-linux

On Thu, Mar 24, 2016 at 2:03 PM, Труб Илья wrote: > > Thanks for your answer, Dmitry. I will look for examples of module maps in > test sources. You shouldn't need to. If you have built Swift for arm, you should have the right one produced by the build system. How did you

Re: [swift-dev] LazyFilterCollection is not a Collection

On Mon, May 9, 2016 at 11:46 AM, Rob Napier wrote: > It violates the performance requirements. > CollectionType.count requires O(1) access if Index is a > RandomAccessIndexType. Hi Rob, We don't have RandomAccessIndexType anymore. Dmitri --

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

On Wed, May 11, 2016 at 2:53 PM, Russ Bishop via swift-dev wrote: > I’m implementing SE-0017 but based on the standard library guidelines I think > Unmanaged should have initializers that take > UnsafePointer/UnsafeMutablePointer and vice-versa which would fit more >

Re: [swift-dev] Argument unused warnings

On Tue, May 17, 2016 at 12:37 PM, Daniel Dunbar via swift-dev wrote: > Something broke yesterday causing Swift to report gobs of argument unused > warnings, see: > https://bugs.swift.org/browse/SR-1546 > for a reference. > > Does anyone know who this should go to?

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

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

Re: [swift-dev] Why are we re-linking?

On Fri, May 6, 2016 at 9:16 AM, Jordan Rose wrote: > Hm. That might be a nice balance, and it’s not entirely a lie: that’s the > version of the compiler that you’re using, if not the stdlib and runtime. > I’d still like to put it behind a flag, so that we can turn it off it

Re: [swift-dev] Cross-compiling (nearly) everything for RPi from OSX

On Mon, May 9, 2016 at 7:11 PM, Karl Wagner via swift-dev wrote: > Does anybody (or any bots) install directly from the build script? Yes, that's how all Swift builds are done. Dmitri -- main(i,j){for(i=2;;i++){for(j=2;j

Re: [swift-dev] repl/test-repl-glibc.py Failure on Ubuntu

+Brian On Thu, Apr 14, 2016 at 2:46 PM, Ryan Lovelett via swift-dev wrote: > I've played around with `git bisect` and I think I've tracked it down to > this commit [1]. Which came from PR #1704 [2]. I've also updated the issue, > SR-1109, to include this information. > >

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

Right. The primary testsuite was not running since yesterday because of my build-script changes. Dmitri On Tue, Apr 19, 2016 at 12:22 PM, Greg Parker wrote: > Dmitri, your commit 265fa20c re-enabled tests that were previously not > running, correct? > > > On Apr 19, 2016,

Re: [swift-dev] Importing .swift file into REPL?

On Wed, Apr 20, 2016 at 3:23 PM, Austin Zheng via swift-dev wrote: > Hello developers, > > Is there a way to import a .swift source file into the interactive REPL? > There are times I'd like to debug code by importing it into the REPL and then > typing in various

Re: [swift-dev] Standard Library not built in release mode with -R in build script

On Thu, Jul 21, 2016 at 8:35 AM, Ankit Agarwal via swift-dev wrote: > Standard library is not built in release mode by default with -R flag in > build script. Is that intended behaviour? > > Passing `--no-swift-stdlib-assertions --build-swift-static-stdlib >

Re: [swift-dev] Descriptive Protocol non-conformance errors

On Sun, Jul 17, 2016 at 7:41 AM, Sean Alling via swift-dev wrote: > Sorry for the late reply, > > Ted: > > A JIRA? I know that’s issue tracking, where can I get one of those? It is located here: https://bugs.swift.org/ . Dmitri --

Re: [swift-dev] [swift-evolution] Endgame for Swift 3

On Fri, Jul 15, 2016 at 11:44 AM, Ted kremenek via swift-dev wrote: > Good question. > > Dave/Dmitri: do you have a recommendation here? I can see either the JIRA > issues referencing the proposal (if one exists) or updating the gist. I > prefer the former. Updating the

Re: [swift-dev] Implementation of Type Erasers

On Mon, Sep 5, 2016 at 11:13 AM, Chris Eidhof via swift-dev wrote: > Hello swift-dev, > > I was wondering why type erasers (e.g. for AnyIterator) are implemented the > way they are. I would implement AnyIterator like this: > > final class MyAnyIterator: IteratorProtocol { >

Re: [swift-dev] Question about dump-ast and logging the output to file

On Wed, Aug 24, 2016 at 10:27 AM, Marcel Rebouças wrote: > Hello everybody, > > I am planning in doing some research and analysis with the ASTs of swift > programs and, for that reason, I am trying to modify the compiler to always > generate a file with the contents of the