Re: [swift-dev] Proposal: Opaque SIL values

2017-01-25 Thread John McCall via swift-dev
> On Jan 25, 2017, at 9:13 PM, Joe Groff via swift-dev > wrote: > Looks great. One nitpick: > >> Naturally, opaque types must limit some optimizations, such as inlining. > > I don't see how opaque types by themselves prevent inlining. You can inline a > generic into another generic, or a funct

Re: [swift-dev] Proposal: Opaque SIL values

2017-01-25 Thread Chris Lattner via swift-dev
On Jan 24, 2017, at 10:58 PM, Andrew Trick wrote: > > That would come about when the program wants to use the same lvalue for > multiple real values. I don't expect many problems with simple opaque types. > The only way to mutate them is either passing them @inout or returning them > @out. We

Re: [swift-dev] Proposal: Opaque SIL values

2017-01-25 Thread Joe Groff via swift-dev
Looks great. One nitpick: > Naturally, opaque types must limit some optimizations, such as inlining. I don't see how opaque types by themselves prevent inlining. You can inline a generic into another generic, or a function using a resilient type into another function. > This would hide part of

Re: [swift-dev] CI outage tomorrow for upgrade

2017-01-25 Thread mishal_shah via swift-dev
CI upgrade completed. Note: You will need Xcode 8.3 Beta 1 to be able to build master and swift-3.1-branch. Thanks, Mishal Shah > On Jan 25, 2017, at 11:11 AM, mishal_shah wrote: > > Starting the upgrade process, please avoid triggering PR testing. > > Thanks, > Mishal Shah >> On Jan 24,

Re: [swift-dev] Proposal: Opaque SIL values

2017-01-25 Thread Karl Wagner via swift-dev
> On 24 Jan 2017, at 20:10, Andrew Trick via swift-dev > wrote: > > I’m sending out a proposal for fundamentally changing SIL. This work feeds > into generic code optimization, resilience, semantic ARC, and SIL ownership. > This was discussed at length back in October—some info went out on >

Re: [swift-dev] CI outage tomorrow for upgrade

2017-01-25 Thread mishal_shah via swift-dev
Starting the upgrade process, please avoid triggering PR testing. Thanks, Mishal Shah > On Jan 24, 2017, at 1:49 PM, Nicole Jacque via swift-dev > wrote: > > Hi All- > > We will have a CI outage for a couple of hours tomorrow starting at 11 > Pacific, in order to upgrade the CI machines to

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

2017-01-25 Thread Erik Eckstein via swift-dev
> On Jan 24, 2017, at 10:52 PM, Andrew Trick wrote: > > So it looks like the Foundation tests haven’t been run for a few builds. > Taking a wild guess, could this have something to do with mangling Erik? > Unlikely___ swift-dev mailing list swift-de

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

2017-01-25 Thread Arnold Schwaighofer via swift-dev
This is most likely a CMake dependency failure that goes away when you do a clean build. oss-swift-incremental-RA-linux-ubuntu-16_10: undefined symbol: _TFsoi1pu0_Rxs26RangeReplaceableCollection_S_Wx8Iterator7Element_zW_S0_S1__rFTxq__x https://bugs.swift.org/browse/SR-3621 > On Jan 24, 2017,

[swift-dev] [Swift CI] Build Still Failing: 1. OSS - Swift (Tools Opt+Assert, Stdlib Opt+DebInfo+Assert, Resilience) - macOS (master) #90

2017-01-25 Thread no-reply--- via swift-dev
New issue found!Title: Report [FAILURE] oss-swift_tools-RA_stdlib-RDA_test-macos-resilience [#90] Build URL:https://ci.swift.org/job/oss-swift_tools-RA_stdlib-RDA_test-macos-resilience/90/ Project:oss-swift_tools-RA_stdlib-RDA_test-macos-resilience Date of build:Wed, 25 Jan 2