[swift-dev] Swift build fails with "error: unable to load standard library for target 'ppc64le-unknown-linux'".

Hi,   I am trying to build Swift on ppc64le platform running Ubuntu 16.04. Swift master branch top-of-the-tree code is cloned from github. I am getting following error during the build process:   <... build log from beginning till here removed ...> --- bootstrap: note: building runtime v3 target: P

Re: [swift-dev] SR-3423 Starter questions

> On Nov 11, 2017, at 2:59 PM, Mohammed Ennabah via swift-dev > wrote: > > I dug into the codebase as stated in the steps you mentioned, and tried to > change one of the errors to see if it really change when I use Swift REPL, > but nothing changed. Is it possible that I change something and d

Re: [swift-dev] SR-3423 Starter questions

> On Nov 13, 2017, at 6:00 AM, Brent Royal-Gordon via swift-dev > wrote: > >> On Nov 11, 2017, at 2:59 PM, Mohammed Ennabah via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> I dug into the codebase as stated in the steps you mentioned, and tried to >> change one of the errors to see

Re: [swift-dev] SR-3423 Starter questions

> On Nov 13, 2017, at 4:00 PM, Brent Royal-Gordon > wrote: > >> On Nov 11, 2017, at 2:59 PM, Mohammed Ennabah via swift-dev >> mailto:swift-dev@swift.org>> wrote: >> >> I dug into the codebase as stated in the steps you mentioned, and tried to >> change one of the errors to see if it really

Re: [swift-dev] SR-3423 Starter questions

> On Nov 13, 2017, at 4:00 PM, Brent Royal-Gordon > wrote: > >> On Nov 11, 2017, at 2:59 PM, Mohammed Ennabah via swift-dev >> wrote: >> >> • I dug into the codebase as stated in the steps you mentioned, and >> tried to change one of the errors to see if it really change when I use >

Re: [swift-dev] SR-3423 Starter questions

It sounds like you haven't run the 'utils/update-checkout --clone' script. That pulls down the cmark repository, and so should take care of that error. The Swift README has step-by-step instructions, which I think mention the 'update-checkout' script. You may want to try following those from top t

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

On Mon, Nov 6, 2017 at 6:54 PM, Jacob Bandes-Storch via swift-evolution < swift-evolut...@swift.org> wrote: > Over a year ago, we discussed adding a magic "allValues"/"allCases" static > property on enums with a compiler-derived implementation. The original > proposal > PR

Re: [swift-dev] Preparing metadata records for ABI stability

> On Nov 7, 2017, at 8:58 PM, Joe Groff via swift-dev > wrote: > > I’m trying to plan out changes to our type metadata record formats for ABI > stability. I’ll start by looking at the current situation and then make > suggestions about things we ought to change. We want to settle on a design

Re: [swift-dev] Preparing metadata records for ABI stability

> On Nov 13, 2017, at 11:40 AM, John McCall via swift-dev > wrote: > > - I feel like we're not boxing ourselves in too much to assume a layout of > the generic requirements. Having a base offset already imposes a pretty > steep compatibility requirement — e.g. even if we significantly gene

Re: [swift-dev] Preparing metadata records for ABI stability

> On Nov 13, 2017, at 2:42 PM, Slava Pestov wrote: > > >> On Nov 13, 2017, at 11:40 AM, John McCall via swift-dev > > wrote: >> >> - I feel like we're not boxing ourselves in too much to assume a layout of >> the generic requirements. Having a base offset alread

Re: [swift-dev] Preparing metadata records for ABI stability

On Nov 13, 2017, at 11:40 AM, John McCall wrote: > > >> On Nov 7, 2017, at 8:58 PM, Joe Groff via swift-dev > > wrote: >> >> I’m trying to plan out changes to our type metadata record formats for ABI >> stability. I’ll start by looking at the current situation and t

Re: [swift-dev] Preparing metadata records for ABI stability

> On Nov 13, 2017, at 4:30 PM, Joe Groff wrote: > > On Nov 13, 2017, at 11:40 AM, John McCall > wrote: >> >> >>> On Nov 7, 2017, at 8:58 PM, Joe Groff via swift-dev >> > wrote: >>> >>> I’m trying to plan out changes to our type metadata

Re: [swift-dev] Preparing metadata records for ABI stability

> On Nov 13, 2017, at 2:16 PM, John McCall wrote: > >> >> On Nov 13, 2017, at 4:30 PM, Joe Groff > > wrote: >> >> On Nov 13, 2017, at 11:40 AM, John McCall > > wrote: >>> >>> On Nov 7, 2017, at 8:58 PM, Joe Groff via swift-dev >>>

[swift-dev] Swift CI will be down for maintenance - Nov 13th 2017 - 6pm PST

We will be taking down ci.swift.org for maintenance today Nov 13th 2017 at 6pm PST I will reply to this email once the maintenance has started and completed. Thanks, Mishal Shah ___ swift-dev mailing list swift-dev@swift.org ht

Re: [swift-dev] SR-3423 Starter questions

> On Nov 13, 2017, at 9:52 AM, Mohammed Ennabah wrote: > > I’m not sure what I’m missing when I build "utils/build-scrip”, but I keep > getting > "can't find source directory for cmark (tried > /Users/Mohammed/swift-source/cmark)” > > Just to know: I mkdir “swift-source” and then cloned the pr

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

> On Nov 12, 2017, at 10:16 AM, Xiaodi Wu wrote: > > On Sun, Nov 12, 2017 at 4:54 AM, Brent Royal-Gordon > wrote: >> On Nov 10, 2017, at 11:01 PM, Xiaodi Wu > > wrote: >> >> Nit: if you want to call it `ValueEnumerable`, then this shoul

Re: [swift-dev] Swift CI will be down for maintenance - Nov 13th 2017 - 6pm PST

Maintenance started. > On Nov 13, 2017, at 4:50 PM, Mishal Shah wrote: > > We will be taking down ci.swift.org for maintenance > today Nov 13th 2017 at 6pm PST > > I will reply to this email once the maintenance has started and completed. > > Thanks, > Mishal Shah >

Re: [swift-dev] Swift CI will be down for maintenance - Nov 13th 2017 - 6pm PST

Maintenance completed. > On Nov 13, 2017, at 6:18 PM, Mishal Shah wrote: > > Maintenance started. > >> On Nov 13, 2017, at 4:50 PM, Mishal Shah > > wrote: >> >> We will be taking down ci.swift.org for maintenance >> today Nov 13th 2017 at 6

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

On Mon, Nov 13, 2017 at 8:16 PM, Brent Royal-Gordon wrote: > On Nov 12, 2017, at 10:16 AM, Xiaodi Wu wrote: > > On Sun, Nov 12, 2017 at 4:54 AM, Brent Royal-Gordon < > br...@architechies.com> wrote: > >> On Nov 10, 2017, at 11:01 PM, Xiaodi Wu wrote: >> >> Nit: if you want to call it `ValueEnum

Re: [swift-dev] [swift-evolution] Re-pitch: Deriving collections of enum cases

On Mon, Nov 13, 2017 at 11:15 PM, Xiaodi Wu wrote: > On Mon, Nov 13, 2017 at 8:16 PM, Brent Royal-Gordon < > br...@architechies.com> wrote: > >> On Nov 12, 2017, at 10:16 AM, Xiaodi Wu wrote: >> >> On Sun, Nov 12, 2017 at 4:54 AM, Brent Royal-Gordon < >> br...@architechies.com> wrote: >> >>> On

[swift-dev] RFC: AST representation for coroutine types

SIL now has some minimal representational support for coroutines, and while there's significantly more to do there, I'd like to simultaneously kick off a conversation about how best to represent them at the AST level. Only special kinds of declarations can be coroutines. In the first stage, tha

[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] Preparing metadata records for ABI stability

> On Nov 13, 2017, at 5:19 PM, Joe Groff wrote: > >> On Nov 13, 2017, at 2:16 PM, John McCall > > wrote: >> >>> >>> On Nov 13, 2017, at 4:30 PM, Joe Groff >> > wrote: >>> >>> On Nov 13, 2017, at 11:40 AM, John McCall >>