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

> On Dec 13, 2017, at 10:28 PM, John McCall via swift-dev > wrote: > >> On Dec 13, 2017, at 8:35 PM, Saleem Abdulrasool > > wrote: >> >>> On Wed, Dec 13, 2017 at 4:14 PM, John McCall >> > wrote: > >>> >>> - SILGen may need to introdu

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

> On Dec 13, 2017, at 10:47 PM, Atul Sowani via swift-dev > wrote: > > 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 int

Re: [swift-dev] Request for review on Windows CMake changes

> On Dec 12, 2017, at 6:06 PM, Saleem Abdulrasool via swift-dev > wrote: > > The problems with the cross-compiling that Im referring to are not inherent > to CMake (although, I am slightly partial to the autotools approach to > cross-compilation), but rather the way that the tool is being use

Re: [swift-dev] Help request for test failure "IRGen/objc_simd.sil".

> On Dec 8, 2017, at 1:49 AM, Atul Sowani via swift-dev > wrote: > > Hi, > > I am getting following failure while running IRGen/objc_simd.sil on ppc64le > (Ubuntu 16.04). > > # /bin/bash objc_simd.sil.script > /root/swift-source/swift/test/IRGen/objc_simd.sil:60:23: error: expected > string

[swift-dev] Bug for FIXME(sil-serialize-all) @_inlineable cleanup?

Many stdlib functions were temporarily marked @_inlineable in the fallout of killing sil-serialize-all. Where is the bug report tracking their resolution? The C runtime currently needs to export otherwise-private symbols so they can be called by such functions. Those symbols can't be un-exported

Re: [swift-dev] Default deployment target for swiftc

There should not be any availability checks required in the common fast-prototyping case, where your SDK version and your running OS version are the same. Availability checks are required when some API has changed since the OS version that is your deployment target. In the fast-prototyping sce

Re: [swift-dev] No attribute(swiftcall) support on Linux?

> On Nov 14, 2017, at 7:52 AM, Arnold Schwaighofer > wrote: > >> On Nov 14, 2017, at 12:33 AM, Slava Pestov via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> > >>> On Nov 13, 2017, at 10:47 PM, Greg Parker via swift-dev >>> mail

[swift-dev] No attribute(swiftcall) support on Linux?

I see that in our Linux builds clang complains that it does not support the swiftcall attribute. In file included from /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/swift/unittests/runtime/Metadata.cpp:13: /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/s

Re: [swift-dev] Rationalizing FloatingPoint conformance to Equatable

> On Oct 26, 2017, at 11:47 AM, Xiaodi Wu via swift-dev > wrote: > > On Thu, Oct 26, 2017 at 1:30 PM, Jonathan Hull > wrote: > Now you are just being rude. We all want Swift to be awesome… let’s try to > keep things civil. > > Sorry if my reply came across that way! Th

Re: [swift-dev] Question: memory management on Stack with Structs ?

> On Oct 18, 2017, at 6:05 PM, Thibault Wittemberg via swift-dev > wrote: > > Hi everyone, > > I am a member of the RxSwiftCommunity, and I am facing an issue on a PR that > I've made (https://github.com/RxSwiftCommunity/NSObject-Rx/pull/49 >

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

Probably Andy's https://github.com/apple/swift/pull/12420. Automatic revert didn't work, and I won't be able to revert manually for a few hours. > On Oct 17, 2017, at 2:48 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-ASAN-RA-osx [#443] > > Build URL:https://ci.swift.or

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.04 - Long Test (master) #447

Missing build dependency somewhere? [7/78] Generating swiftDispatch.o, swift/Dispatch.swiftmodule, swift/Dispatch.swiftdoc FAILED: src/swiftDispatch.o src/swift/Dispatch.swiftmodule src/swift/Dispatch.swiftdoc cd /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_04-lon

Re: [swift-dev] Strange Linux smoke test failures?

> On Oct 17, 2017, at 8:16 PM, David Zarzycki via swift-dev > wrote: > > I’m trying to get pull request 12496 to pass the smoke test, but it seems to > be repeatedly failing the Linux smoke test in bizarre, unrelated, and > unexpected ways. Does anybody have some theories about what might be

Re: [swift-dev] Test case "tuple_arguments.swift" failed when compiler is built in debug mode on x86_64

> On Oct 16, 2017, at 9:20 AM, Sam Ding via swift-dev > wrote: > I test the case "tuple_arguments.swift" for v4.0 and found it is failed when > the swift compiler is built in "-d" debug mode, but it is passed > when built in release mode. > Here is a simple test case: > > // SR-4738 > > let

[swift-dev] Segfaults in swift-build bootstrap on Linux?

I have seen two PR test runs today on Linux that have crashed in swift-build bootstrap. Is anyone tracking this? https://ci.swift.org/job/swift-PR-Linux-smoke-test/1381 https://ci.swift.org/job/swift-PR-Linux/702

[swift-dev] Code that uses the is-Swift metadata bit

I'm looking for all code that uses the is-Swift bit in class metadata. Uses that I know of: * Compiler-generated class metadata (addClassDataPointer() in GenMeta.cpp) * Runtime metadata checks (isTypeMetadata() inMetadata.h) * Stuff in lldb and other debugging tools * Stuff in the Objective-C runt

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

> On Sep 27, 2017, at 10:39 AM, John McCall via swift-dev > wrote: > >> On Sep 27, 2017, at 1:24 PM, Jiho Choi > > wrote: >> >> Thanks for the explanation. I modified those two locations you mentioned >> but the build failed during tests. I've been browsing the sou

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

Re: [swift-dev] What can you change in a fixed-contents struct?

> On Sep 5, 2017, at 11:59 AM, Jordan Rose via swift-dev > wrote: > > Hey, all. In preparation for the several proposals we have to come this year, > I cleaned up docs/LibraryEvolution.rst > a little bit based on what's > changed in Swift 4. This i

Re: [swift-dev] Pathway to becoming an effective contributor

> On Jun 20, 2017, at 12:37 PM, Halen Wooten via swift-dev > wrote: > > Hi, > > I would like to start a discussion about getting started with the > Swift Compiler. The end goal is to see if there are ways we can help > newcomers to the compiler get started and more quickly grow into a > more e

Re: [swift-dev] statically initialized arrays

> On Jun 19, 2017, at 9:58 AM, Joe Groff wrote: > >> On Jun 15, 2017, at 8:30 PM, Greg Parker via swift-dev >> wrote: >> >> swift_once is not the most efficient solution here - we don't need separate >> once token storage in this case - but it's

Re: [swift-dev] statically initialized arrays

> On Jun 15, 2017, at 4:39 PM, Andrew Trick via swift-dev > wrote: > >> On Jun 15, 2017, at 4:26 PM, Andrew Trick > > wrote: >> >>> On Jun 14, 2017, at 12:03 PM, Jordan Rose via swift-dev >>> mailto:swift-dev@swift.org>> wrote: >>> ad 3) IRGen support

Re: [swift-dev] statically initialized arrays

> On Jun 15, 2017, at 9:24 AM, John McCall via swift-dev > wrote: > >> On Jun 15, 2017, at 10:52 AM, Arnold via swift-dev >> wrote: >> >>> On Jun 14, 2017, at 2:56 PM, Dave Abrahams via swift-dev >>> wrote: >>> on Wed Jun 14 2017, Erik Eckstein wrote: I’m about implementi

Re: [swift-dev] Override the path to the Swift compiler?

> On May 30, 2017, at 4:48 PM, Jimmy Yue via swift-dev > wrote: > > Hey Swift Devs, > > Does there happen to be an environment variable, similar to 'CC' for C, that > I could use to override the path to the Swift compiler? If so, is there also > one for ibtool, metal, etc.? > > I want to re

Re: [swift-dev] Xcode pauses when I add a toolchain

> On May 12, 2017, at 12:18 PM, David Ungar via swift-dev > wrote: > > Whenever I change the contents of /Library/Developer/Toolchains, Xcode spods > for a bit, then spods again. I thought this was normal till I noticed that it > does not happen on my colleague’s machine. Any thoughts for wha

Re: [swift-dev] Mysterious memory improvement and regression

> On Apr 24, 2017, at 8:52 PM, Pavol Vaskovic wrote: > >> On 25 Apr 2017, at 01:28, Greg Parker wrote: >> >> The value of MAX_RSS depends on OS behavior. Other activity on the same >> machine may change MAX_RSS of the benchmark. > > Can you please describe the mechanism of how “other activit

Re: [swift-dev] Mysterious memory improvement and regression

> On Apr 21, 2017, at 3:57 AM, Pavol Vaskovic via swift-dev > wrote: > > Hi swift-dev! > > I was working over the Easter holiday weekend on script that reports the > benchmark results comparison. I wasn’t always up-to-date with the master, but > I have noticed a mysterious change in MAX_R

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

Michael, one of your changes broke all three ASAN bots. Please fix or revert ASAP. (Could this be related to https://github.com/apple/swift/pull/8169 ? I didn't confirm that the bot's change lists are correct.) > On Mar 18, 2017, at 11:48 AM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-

Re: [swift-dev] Statically-emitted or statically-allocated objects with new refcounting

> On Mar 17, 2017, at 4:07 PM, Joe Groff wrote: > >> On Mar 17, 2017, at 4:04 PM, Greg Parker > > wrote: >> >>> On Mar 17, 2017, at 8:19 AM, Joe Groff >> > wrote: >>> >>> It might at some point, but I was thinking of using this in the runtime

Re: [swift-dev] Statically-emitted or statically-allocated objects with new refcounting

> On Mar 17, 2017, at 8:19 AM, Joe Groff wrote: > > >> On Mar 16, 2017, at 9:02 PM, Greg Parker wrote: >> >>> >>> On Mar 16, 2017, at 7:35 PM, John McCall wrote: >>> >>>> On Mar 16, 2017, at 4:23 PM, Joe Groff wrote: >&g

Re: [swift-dev] Statically-emitted or statically-allocated objects with new refcounting

> On Mar 16, 2017, at 7:35 PM, John McCall wrote: > >> On Mar 16, 2017, at 4:23 PM, Joe Groff wrote: >> >>> On Mar 14, 2017, at 3:53 PM, Greg Parker via swift-dev >>> wrote: >>> >>>> On Mar 14, 2017, at 2:16 PM, John McCall wrote:

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

This was https://github.com/apple/swift/pull/8099 . I reverted it. The rest of you are off the hook. > On Mar 14, 2017, at 11:31 PM, Greg Parker via swift-dev > wrote: > > I don't know what broke here, so I'm going to revert all of these changes in > about an hour u

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

I don't know what broke here, so I'm going to revert all of these changes in about an hour unless somebody knows what is wrong. • IRGen: Consider the conforming type’s accessibility for lazy witness (detail) • [sil-generic-specializer] Provide a possibility to disable the (detai

Re: [swift-dev] Statically-emitted or statically-allocated objects with new refcounting

> On Mar 14, 2017, at 2:16 PM, John McCall wrote: > >> On Mar 14, 2017, at 5:08 PM, Jordan Rose via swift-dev > <mailto:swift-dev@swift.org>> wrote: >> >>> On Mar 14, 2017, at 13:52, Greg Parker via swift-dev >> <mailto:swift-dev@swift.org>&

Re: [swift-dev] Statically-emitted or statically-allocated objects with new refcounting

> On Mar 14, 2017, at 1:34 PM, Greg Parker via swift-dev > wrote: > > >> On Mar 14, 2017, at 12:43 PM, Joe Groff > <mailto:jgr...@apple.com>> wrote: >> >> Hey Greg, what are the correct refcounting bits now to set in a global >> statically-emi

Re: [swift-dev] Statically-emitted or statically-allocated objects with new refcounting

> On Mar 14, 2017, at 12:43 PM, Joe Groff wrote: > > Hey Greg, what are the correct refcounting bits now to set in a global > statically-emitted heap object that shouldn't ever be released? For now use the same thing that stack-allocated objects use. I forget what the bit pattern is exactly.

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

Thanks, Robert. > On Mar 13, 2017, at 10:13 PM, Robert Widmann wrote: > > This one is mine and will be resolved shortly. Practical Swift and I have > been stepping on each others toes trying to introduce and fix the same > crashes. > > ~Robert Widmann > >> On Mar 14, 2017, at 1:04 AM, no-r

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

Password expired. -- scp toolchain tar -- WARNING: Your password has expired. Password change required but no TTY available. Build step 'Execute shell' marked build as failure > On Mar 13, 2017, at 7:22 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-package-linux-ubuntu-16_04 [#605] > > B

Re: [swift-dev] JIT-ting Swift

What exactly does your code that 'passes argc=1 and argv=["foo"]' look like? Did you null-terminate argv as is required? > On Mar 10, 2017, at 1:45 AM, Alex Denisov via swift-dev > wrote: > > Thank you everybody for your hints and suggestions. It helped me a lot! > I have found the source of

Re: [swift-dev] Marking a function as __attribute__((weak))

> On Mar 6, 2017, at 5:48 PM, Philippe Hausler via swift-dev > wrote: > > Is there a way to mark a function in swift (on Linux) to use the same > emission strategy as weak declarations in c? > > I was to tinkering with some ideas on fixing some poor behavior in > swift-corelibs-foundation a

Re: [swift-dev] master fails to build

> On Feb 11, 2017, at 10:46 AM, Ben Ng via swift-dev > wrote: > > I can’t seem to build master right now: > > git pull > ./utils/update-checkout --clone-with-ssh > ./utils/build-script --release --assertions > > (…) > > [17/558] Linking CXX shared library lib/swift/macosx/x86_64/libswiftCore

Re: [swift-dev] No return functions and program exit

> On Feb 6, 2017, at 9:48 AM, Michael Gottesman via swift-dev > wrote: > > One thing that is an issue that has come up with ownership is that at the SIL > level we do not distinguish in between exceptional noreturn functions and > exceptional return functions. > > This is important since in

Re: [swift-dev] Resilient dynamic dispatch ABI. Notes and mini-proposal.

> On Feb 4, 2017, at 2:35 AM, Andrew Trick via swift-dev > wrote: > > >> On Feb 3, 2017, at 9:37 PM, John McCall > > wrote: >> IV. The function that performs the lookup: IV1) is parameterized by an isa IV2) is not parameterized by an isa IV1 al

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

Failed during package construction, I think: -- scp code sign tar -- WARNING: Your password has expired. Password change required but no TTY available. Build step 'Execute shell' marked build as failure > On Feb 2, 2017, at 6:41 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-package-linu

Re: [swift-dev] Using git-clang-format in the Swift compiler code base.

> On Jan 26, 2017, at 2:07 AM, Andrew Trick via swift-dev > wrote: > > Before I pull in a large PR that "accidentally" reformats a bunch of code, I > want to get feedback on how Swift compiler devs plan to use `clang-format`. > (BTW, here's the PR https://github.com/apple/swift/pull/6922). >

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

IIRC I saw something like this earlier this week, probably Tuesday, but I can't remember if it was in a CI PR build or in a local build on rad-main. > On Dec 21, 2016, at 5:35 PM, Jordan Rose via swift-dev > wrote: > > This can't possibly be me. > > Compile Swift Module 'Get' (9 sources) > V

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

Smells like a missing build dependency somewhere. > On Dec 14, 2016, at 5:40 PM, Slava Pestov via swift-dev > wrote: > > Does anyone know what happened here? It doesn’t look like any of the patches > in the blame log could have caused this: > > /Users/buildnode/jenkins/workspace/oss-swift-in

Re: [swift-dev] Way to --clean only the Swift parts of Swift?

> On Dec 12, 2016, at 9:30 AM, Alexis via swift-dev wrote: > > I find that build-script tends to get corrupted state very easily, forcing me > to do a —clean build. This is usually because of git, but seemingly from > benign things like checking out HEAD~1. Since I’m working on the stdlib, the

Re: [swift-dev] Build failing on CMakeTestCCompiler.cmake

> On Dec 8, 2016, at 7:28 AM, Frederick Kellison-Linn via swift-dev > wrote: > > Hello, > > I have been attempting to build Swift, but have been running into issues near > the end of the build. Specifically, CMake fails on the step [2112/2254] > Performing configure step for 'compiler-rt’, s

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

I wonder if running compiler_crashers with guard malloc set would make most of the indeterminisms go away. > On Dec 7, 2016, at 4:53 PM, Xi Ge via swift-dev wrote: > > I’ll disable it for now. > > >> On Dec 7, 2016, at 4:50 PM, Douglas Gregor > > wrote: >> >> this

Re: [swift-dev] No commit emails

FWIW most commits go through GitHub pull requests nowadays, so setting up GitHub's notifications for the apple/swift repository will keep you informed of most changes. > On Dec 1, 2016, at 11:53 AM, Kenny Leung via swift-dev > wrote: > > Hi All. > > Just a heads up. > > We got a big bolus

Re: [swift-dev] Initializing constant object graph with cycles

> On Nov 4, 2016, at 2:57 AM, Anton Mironov via swift-dev > wrote: > > Hi all, > > I want to initialize constant object graph with cycles. I've considered two > workarounds, but this is not a way I want it to be. > > Here is an example: > ``` > // I have a context > protocol Context : class

Re: [swift-dev] Having 64-bit swift_retain/release ignore all negative pointer values

> On Oct 13, 2016, at 10:46 AM, John McCall via swift-dev > wrote: > >> On Oct 13, 2016, at 9:04 AM, Joe Groff via swift-dev > > wrote: >> >>> On Mar 1, 2016, at 1:33 PM, Joe Groff via swift-dev >> > wrote: >>> >>> In swift_retain/releas

Re: [swift-dev] Validating ABI consistency between runtime C++ and standard library Swift code

> On Oct 12, 2016, at 11:11 AM, John McCall via swift-dev > wrote: > >> On Oct 11, 2016, at 8:10 PM, Joe Groff via swift-dev >> wrote: >> I just tracked down a bug due to C++ code in the Swift runtime code trying >> to interface with standard library code written in Swift, but getting the >

[swift-dev] Starter bug: SR-2875 Emit objc_allocWithZone(cls) instead of [cls allocWithZone:nil]

A starter bug for someone who wants to dip their toes into the Swift compiler: SR-2875 Emit objc_allocWithZone(cls) instead of [cls allocWithZone:nil] https://bugs.swift.org/browse/SR-2875 swiftc currently emits calls to [cls allocWithZone:nil] when constructing Objective-C objects. It should e

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

n: >>> https://github.com/apple/swift/pull/4361 >>> <https://github.com/apple/swift/pull/4361> >>> to finish testing, which it looks like is close. >>> >>> - Daniel >>> >>>> On Aug 17, 2016, at 4:54 PM, Greg Parker vi

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

e/swift/pull/4361 > <https://github.com/apple/swift/pull/4361> > to finish testing, which it looks like is close. > > - Daniel > >> On Aug 17, 2016, at 4:54 PM, Greg Parker via swift-dev > <mailto:swift-dev@swift.org>> wrote: >> >> This is about t

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

This is about to break all of the bots. When do you expect a fix? > On Aug 17, 2016, at 4:28 PM, Max Moiseev via swift-dev > wrote: > > Unfortunate but expected. Need this change in the SwiftPM in order to test > the https://github.com/apple/swift/pull/4361 >

Re: [swift-dev] [RFC] Finer grained OS checks

> On Jul 11, 2016, at 9:50 AM, Karl Wagner via swift-dev > wrote: > > - Also don't like the simulator condition variable. The iOS simulator is > literally x86 iOS. If there was an x86 iPhone, theoretically your binaries > would be compatible. The fact that it runs on a simulator instead of a

Re: [swift-dev] JIRA labels (no worries)

> On May 27, 2016, at 10:05 AM, Brian Gesiak via swift-dev > wrote: > > Hey Jordan, > > Thanks for the email! Very good point -- and I definitely felt weird > assigning "Swift 3" labels to tasks, considering it's not up to me to decide > what goes into Swift 3 or not. Still, I think it's hel

Re: [swift-dev] How to run the tests out-of-tree?

> On May 12, 2016, at 7:45 AM, Karl via swift-dev wrote: > > So I’ve been working on cross-compiling for ARM, and it seems pretty good - > only a bit of refactoring of the build script really needed. It’s a popular > request, the lack of which is hindering lots of people and businesses who >

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

> On Apr 22, 2016, at 4:13 PM, Greg Parker wrote: > > >> On Apr 22, 2016, at 3:14 PM, no-re...@swift.org wrote: >> >> [FAILURE] oss-swift-incremental-RA-osx [#3573] >> >> Build URL: https://ci.swift.org/job/oss-swift-incremental-RA-osx/3573/ >> Project: oss-swift-incremental-RA-osx >> D

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

> On Apr 22, 2016, at 3:14 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3573] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-RA-osx/3573/ > Project: oss-swift-incremental-RA-osx > Date of build:Fri, 22 Apr 2016 14:51:48 -0700 > Build d

Re: [swift-dev] test-repl-glibc failure

> On Apr 21, 2016, at 9:20 PM, Daniel Dunbar via swift-dev > wrote: > > What is the status of the Ubuntu packages CI failure: > swift-package-tests :: repl/test-repl-glibc.py > > It has been failing for a while now and I would like to get back to being > able to use @swift-ci please test

[swift-dev] Starter bug: SR-1286 Incorrect memory management in PotentialArchetype::getNestedType

Starter bug: SR-1286 Incorrect memory management in PotentialArchetype::getNestedType https://bugs.swift.org/browse/SR-1286 I diagnosed a memory error that causes a compiler crash, but I didn't fix it. There are several possible changes with potentially different performance trade-offs. There a

Re: [swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - Ubuntu 14.04 (master) #1072

> On Apr 20, 2016, at 5:14 PM, no-re...@swift.org wrote: > > New issue found! > > [FAILURE] oss-swift-package-linux-ubuntu-14_04 [#1072] > > Build URL: > https://ci.swift.org/job/oss-swift-package-linux-ubuntu-14_04/1072/ > Project: oss-swift-package-linux-ubuntu-14_04 > Date of build:

Re: [swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - Ubuntu 15.10 (master) #1059

v >> mailto:swift-dev@swift.org>> wrote: >> >> Xin and I working on a fix for the original problem. >> I think we should _disable_ this test on linux in the meantime and not >> _xfail_ it. >> >> Erik >> >> >>> On Apr

Re: [swift-dev] [Swift CI] Build Still Failing: OSS - Swift Package - Ubuntu 15.10 (master) #1059

Nope, not your fault. This is a pre-existing problem. I'm not sure why the CI system thought that was a new issue. > On Apr 20, 2016, at 2:08 PM, Michael Ilseman wrote: > > > Unexpected Passing Tests (1): > Swift :: 1_stdlib/ArrayTraps.swift.gyb > > I don’t think my c

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

Looks good. Thanks. I agree about the array failure. I mistakenly considered an OS X test in that diagnosis, but the test isn't failing anywhere on OS X. > On Apr 19, 2016, at 10:35 PM, Xin Tong wrote: > > To summarize. I think I fixed the non-determinism in commit > 7d26a472009eae673fd40a04

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

Disabling the pass that way may have caused two more SILOptimizer test failures: https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4351/ I also suspect that the ArrayTraps failure is caused by somethin

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

Thanks. I'll try that. > On Apr 19, 2016, at 9:35 PM, Xin Tong wrote: > > I will check in something to disable the pass. > > -Xin > > > >> On Apr 19, 2016, at 9:34 PM, Greg Parker wrote: >> >> Looks like it was caused by the RR code motion merge >> (https://github.com/apple/swift/pull/20

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

Looks like it was caused by the RR code motion merge (https://github.com/apple/swift/pull/2064). Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf and 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, unless you have a fix in the next few minutes. > On Apr 19,

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

> On Apr 19, 2016, at 7:54 PM, no-re...@swift.org wrote: > > New issue found! > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#4239] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4239/ > Project: oss-swift-incremental-RA-linux-ubuntu-1

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

> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#3504] > > Tests: > > Name: Swift > Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s) > • Failed: Swift.IRGen.module_hash.swift > This may be an older failure recently uncov

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

Dmitri, your commit 265fa20c re-enabled tests that were previously not running, correct? > On Apr 19, 2016, at 12:15 PM, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#4226] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubun

Re: [swift-dev] print buffering

> On Apr 1, 2016, at 2:52 PM, Drew Crawford via swift-dev > wrote: > > We noticed today when running a swift CLI program to a pipe that stdout is > fully buffered (e.g. not unbuffered, not line-buffered). So just now we > committed unbuffering IO to a bunch of CLI programs. > > Is this the

[swift-dev] Web browser extension for SR-nnn links?

Is there a web browser extension developer in the house? I want a Safari extension that transforms SR-nnn text into links to https://bugs.swift.org/browse/SR-nnn . -- Greg Parker gpar...@apple.com Runtime Wrangler ___ swift-dev mailing list

Re: [swift-dev] Swift kernel hacking, compiler options and target triples

> On Mar 28, 2016, at 11:16 AM, Simon Evans via swift-dev > wrote: > > On a related note about compiler options, what could be done about options > such > as enabling/disabling certain instruction sets eg SSE or FP or other such > lowlevel options etc? These wouldn't necessarily always be on o

Re: [swift-dev] [Discussion] New refcount representation

> On Mar 16, 2016, at 1:42 PM, Brent Royal-Gordon > wrote: > > This is damned clever. > >> * Allows inexpensive per-object storage for future features like associated >> references or class extensions with instance variables. > > It sounds like you wouldn't be able to resize an out-of-band r

Re: [swift-dev] Developing Swift in Xcode

> On Mar 16, 2016, at 1:54 PM, Kenny Leung via swift-dev > wrote: > > This is working for me now using > >utils/build-script -x — —reconfigure > > It takes over an hour to build because it doesn’t seem to be as parallel as > the ninja build (less than 3x parallel vs 8x parallel). > > Th

Re: [swift-dev] [Discussion] New refcount representation

> On Mar 15, 2016, at 11:59 PM, Greg Parker via swift-dev > wrote: > > I am considering a new representation for Swift refcounts and other > per-object data. This is an outline of the scheme. Comments and suggestions > welcome. > > Today, each object stores 64-bit

Re: [swift-dev] [Discussion] New refcount representation

> On Mar 16, 2016, at 2:23 PM, John McCall wrote: > >> On Mar 15, 2016, at 11:59 PM, Greg Parker via swift-dev >> wrote: >> I am considering a new representation for Swift refcounts and other >> per-object data. This is an outline of the scheme. Commen

Re: [swift-dev] [Discussion] New refcount representation

> On Mar 16, 2016, at 9:25 AM, Joe Groff wrote: > > This sounds awesome. Should we still consider using a non-pointer isa > representation on 64 bit platforms? 16 bytes per object header is still kinda > big. If we laid out the np-isa bits so that the "side allocation" bit were > the MSB, and

[swift-dev] [Discussion] New refcount representation

I am considering a new representation for Swift refcounts and other per-object data. This is an outline of the scheme. Comments and suggestions welcome. Today, each object stores 64-bits of refcounts and flags after the isa field. In this new system, each object would store a pointer-size field

[swift-dev] Starter bug: SR-946 Unify mutexes in the Swift runtime.

Starter bug: SR-946 Unify mutexes in the Swift runtime. https://bugs.swift.org/browse/SR-946 "The Swift runtime uses two different mutexes internally. Neither one is good. We should write a new swift::mutex or adopt some LLVM mutex that solves these problems. ..." -- Greg Parker gpar...@a

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

> On Mar 14, 2016, at 3:38 PM, Ryan Lovelett via swift-dev > 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 >> to b

Re: [swift-dev] Value-result ABI for small trivial inouts

> On Dec 17, 2015, at 3:34 PM, Joe Groff via swift-dev > wrote: > > On ARMv7 and ARM64, the argument and return register sets are the same Nit: True on arm64. Not true on armv7; the GPR parameters are r0-r3 but GPR return is r0-r1. -- Greg Parker gpar...@apple.com Runtime Wrangler

Re: [swift-dev] Thread safety of weak properties

> On Dec 15, 2015, at 5:32 PM, Kevin Ballard wrote: > >> On Tue, Dec 15, 2015, at 01:38 PM, Greg Parker via swift-dev wrote: >> >> Another solution is to use a handoff lock algorithm. This is what libobjc >> does now. The lock owner stores its thread ID

Re: [swift-dev] Thread safety of weak properties

> On Dec 14, 2015, at 7:51 PM, Mike Ash wrote: > >> On Dec 14, 2015, at 3:19 PM, Greg Parker via swift-dev >> wrote: >> >>> On Dec 14, 2015, at 9:47 AM, John McCall via swift-dev >>> wrote: >>> >>>> On Dec 12, 2015, at 7:04 PM

Re: [swift-dev] Thread safety of weak properties

> On Dec 14, 2015, at 7:39 PM, Kevin Ballard wrote: > >> On Mon, Dec 14, 2015, at 07:34 PM, Greg Parker wrote: >> >>> On Dec 14, 2015, at 7:26 PM, Kevin Ballard via swift-dev >>> wrote: >>> >>>> On Mon, Dec 14, 2015, at 12:19 PM, Gre

Re: [swift-dev] Thread safety of weak properties

> On Dec 14, 2015, at 7:26 PM, Kevin Ballard via swift-dev > wrote: > >> On Mon, Dec 14, 2015, at 12:19 PM, Greg Parker via swift-dev wrote: >> >>> On Dec 14, 2015, at 9:47 AM, John McCall via swift-dev >>> wrote: >>> >>>> On De

Re: [swift-dev] Thread safety of weak properties

> On Dec 14, 2015, at 9:47 AM, John McCall via swift-dev > wrote: > >> On Dec 12, 2015, at 7:04 PM, Chris Lattner wrote: >> #3 sounds like a great approach to me. I agree with Kevin that if we keep >> the object husk approach that any use of a weak pointer that returns nil >> should drop an

Re: [swift-dev] Trouble minimizing test case: code completion

> On Dec 11, 2015, at 10:43 PM, Drew Crawford via swift-dev > wrote: > > I'm experiencing a bug where code completion from an OSX framework target is > not available in its test target. I'm trying to report this in the tracker, > but I'm having trouble minimizing the test case. > > Where I'

Re: [swift-dev] Determining if a crash is a known issue?

> On Dec 9, 2015, at 1:56 PM, Kevin Ballard via swift-dev > wrote: > > When I get a crash in Swift, is there any easy way to figure out if it's > already a known crasher? Not that I know of. > I know there's a bunch of test cases in > validation-test/compiler_crashers{,_2}/ which I assume