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

Can you directly pass arguments to the function crossing the ABI boundary, and can you directly access them on the other side? If so, what you can do is simply synthesize arguments that cross the full range of the bit-representation of the argument types, and validate that you see the same

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

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 ABI slightly wrong and leading to some nasty hard-to-reproduce heisenbugs. While I've narrowed down the bug in this specific case, it seems like

Re: [swift-dev] copy-on-write proposal

> > > :orphan: > > .. highlight:: sil > > === > Copy-On-Write Representation in SIL > === > > .. contents:: > > Overview > > > This document proposes: > > - An ownership attribute to define copy-on-write (COW)

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 4:48 PM, Andrew Trick wrote: >> On Oct 11, 2016, at 2:14 PM, John McCall wrote: >> >>> On Oct 11, 2016, at 11:49 AM, Joe Groff wrote: On Oct 11, 2016, at 11:44 AM, John McCall wrote:

[swift-dev] Is SE-0138 UnsafeRawBufferPointer included in Xcode 8 beta 3?

The release notes of Xcode 8.1 beta 3 said: > Two types have been added to the Swift standard library: > UnsafeRawBufferPointer and UnsafeMutableRawBufferPointer. But I'm getting errors on building sample codes in release notes: ``` *➜ **9:10:46 * DEVELOPER_DIR=/Applications/Xcode-beta.app

[swift-dev] copy-on-write proposal

This is a proposal for representing copy-on-write buffers in SIL. Actually it’s still a draft for a proposal. It also heavily depends on how we move forward with SIL ownership. CopyOnWrite.rst Description: Binary data If you have any comments, please let me know. Erik

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 2:14 PM, John McCall wrote: > >> On Oct 11, 2016, at 11:49 AM, Joe Groff wrote: >>> On Oct 11, 2016, at 11:44 AM, John McCall wrote: >>> On Oct 11, 2016, at 11:22 AM, Joe Groff wrote:

Re: [swift-dev] CI outage tomorrow

Update completed. Please download Xcode 8.1 beta 3 from https://developer.apple.com/download/ Thanks, Mishal Shah > On Oct 11, 2016, at 2:14 PM, mishal_shah via swift-dev > wrote: > > Reminder: > > Starting update right now. > > During the update, please don’t

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 11:49 AM, Joe Groff wrote: >> On Oct 11, 2016, at 11:44 AM, John McCall wrote: >> >>> On Oct 11, 2016, at 11:22 AM, Joe Groff wrote: On Oct 11, 2016, at 11:19 AM, Andrew Trick wrote:

Re: [swift-dev] CI outage tomorrow

Reminder: Starting update right now. During the update, please don’t trigger pull request testing on GitHub. Thanks, Mishal Shah > On Oct 10, 2016, at 6:16 PM, Nicole Jacque via swift-dev > wrote: > > Hi All- > > The CI bots on swift.org will be down temporarily,

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 11:44 AM, John McCall wrote: > >> On Oct 11, 2016, at 11:22 AM, Joe Groff wrote: >>> On Oct 11, 2016, at 11:19 AM, Andrew Trick wrote: >>> >>> On Oct 11, 2016, at 11:02 AM, Joe Groff wrote:

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

On Oct 11, 2016, at 10:10 AM, Michael Gottesman wrote: >> >If ARC Code Motion wishes to move the ARC semantics of ownership qualified >> >load, store instructions, it must now consider read/write effects. On the >> >other hand, it will be able to now not consider the

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 11:19 AM, Andrew Trick wrote: > > >> On Oct 11, 2016, at 11:02 AM, Joe Groff wrote: >> >> >>> On Oct 11, 2016, at 10:50 AM, John McCall wrote: >>> On Oct 11, 2016, at 10:10 AM, Joe Groff via swift-dev

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 11:02 AM, Joe Groff wrote: > > >> On Oct 11, 2016, at 10:50 AM, John McCall wrote: >> >>> On Oct 11, 2016, at 10:10 AM, Joe Groff via swift-dev >>> wrote: On Oct 10, 2016, at 6:58 PM, Andrew Trick

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 10:50 AM, John McCall wrote: > >> On Oct 11, 2016, at 10:10 AM, Joe Groff via swift-dev >> wrote: >>> On Oct 10, 2016, at 6:58 PM, Andrew Trick wrote: >>> >>> On Oct 10, 2016, at 6:23 PM, Joe Groff

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 10:10 AM, Joe Groff via swift-dev > wrote: >> On Oct 10, 2016, at 6:58 PM, Andrew Trick wrote: >> >> >>> On Oct 10, 2016, at 6:23 PM, Joe Groff wrote: >>> >>> On Oct 7, 2016, at 11:10 PM, Andrew Trick via

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 10:33 AM, Andrew Trick wrote: > > >> On Oct 11, 2016, at 10:10 AM, Joe Groff wrote: >> >> >>> On Oct 10, 2016, at 6:58 PM, Andrew Trick wrote: >>> >>> On Oct 10, 2016, at 6:23 PM, Joe Groff

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 11, 2016, at 10:10 AM, Joe Groff wrote: > > >> On Oct 10, 2016, at 6:58 PM, Andrew Trick wrote: >> >> >>> On Oct 10, 2016, at 6:23 PM, Joe Groff wrote: >>> >>> On Oct 7, 2016, at 11:10 PM, Andrew Trick via swift-dev

Re: [swift-dev] [semantic-arc][proposal] High Level ARC Memory Operations

> On Oct 10, 2016, at 8:05 PM, Chris Lattner wrote: > > >> On Oct 7, 2016, at 2:38 PM, Michael Gottesman via swift-dev >> > wrote: >> >> Attached below is an updated version of the proposal. Again a rendered >> version is

Re: [swift-dev] [discussion notes] SIL address types and borrowing

> On Oct 10, 2016, at 6:58 PM, Andrew Trick wrote: > > >> On Oct 10, 2016, at 6:23 PM, Joe Groff wrote: >> >> >>> On Oct 7, 2016, at 11:10 PM, Andrew Trick via swift-dev >>> wrote: >>> ** World 1: SSA @inout >>> >>> Projecting an