[swift-dev] Role of Brace-Stmt in Swift AST

Hi, I am trying to understand the Swift AST by looking at output produced from swiftc -dump-ast . Most of it makes sense to me, but there are some things that I don’t understand. For example, consider the following code: var x = 42 This produces the following output: (source_file (top_level

[swift-dev] Build errors

Hello, In an effort to isolate a different bug, I'm trying to build HEAD of master, and have encountered what looks to be a configuration error. Can somebody please point me in the right direction? Here is the relevant build output - I can post a complete log if it would help. There are many "

Re: [swift-dev] Build errors

On Wed, Mar 23, 2016 at 9:11 AM, George King via swift-dev wrote: > Hello, > > In an effort to isolate a different bug, I'm trying to build HEAD of master, > and have encountered what looks to be a configuration error. Can somebody > please point me in the right direction? Hi George, Which bra

Re: [swift-dev] Role of Brace-Stmt in Swift AST

Hi Toni, What you are seeing is a side-effect of / workaround for the use of top-level executable statements. In general, at the top level of a source file you expect declarations (of types, of functions, etc) and then statements will be inside those declarations (the implementations of free f

Re: [swift-dev] Build errors

I am using stable for both, master for all of the others. clang: 3e4d01d llvm: 56e761d > On Mar 23, 2016, at 12:32 PM, Dmitri Gribenko via swift-dev > wrote: > > On Wed, Mar 23, 2016 at 9:11 AM, George King via swift-dev > wrote: >> Hello, >> >> In an effort to isolate a different bug, I'm t

Re: [swift-dev] large dictionary literal overflows swiftc stack

I ran a test to see the maximum number of elements swift could handle before crashing and the numbers are swift 2.2: 1213 swift 3-dev (mar 16 snapshot): 976 I don't know why swift 3 is lower than swift 2.2, but I'm guessing its due to the same underlying cause, which is running out of stack spa

Re: [swift-dev] large dictionary literal overflows swiftc stack

Thanks for digging into this! I’m seeing the same thing you are - in Swift 3, we’ve solved the problem for array literals, but dictionary literals are still susceptible. I’ll take a look to see why the current round of optimizations aren’t being applied to them. - Joe > On Mar 23, 2016, at 11:

Re: [swift-dev] Role of Brace-Stmt in Swift AST

Hi Greg, Thanks very much for the clear answer. This helps me a lot! Best regards, Toni > On 23 Mar 2016, at 17:53, Greg Titus wrote: > > Hi Toni, > > What you are seeing is a side-effect of / workaround for the use of top-level > executable statements. > > In general, at the top level of a

[swift-dev] long double usage in swift

Hi, I was looking at an ABI related issue on Windows. In trying to construct a test case, it seems that I am unable to import a declaration using a long double into swift. I was wondering if there is something about long double usage in swift that I am unaware of. Inputs/abi.h: float fp32_call

Re: [swift-dev] long double usage in swift

There’s a Float80 type, if you’re looking for an 80-bit floating point value. Alex > On 23 Mar 2016, at 21:25, Saleem Abdulrasool via swift-dev > wrote: > > Hi, > > I was looking at an ABI related issue on Windows. In trying to construct a > test case, it seems that I am unable to import a

Re: [swift-dev] long double usage in swift

Sorry, hit send too quickly: Inputs/abi.h: float fp32_call(void); double fp64_call(void); long double fp80_call(void); Inputs/module.map: module abi { header "abi.h" } test.swift: %swift -I Inputs -parse %s import abi @inline(never) func blackhole(t : T) { } func test_floating_point() {

Re: [swift-dev] long double usage in swift

On Wed, Mar 23, 2016 at 2:28 PM, Alex Blewitt wrote: > There’s a Float80 type, if you’re looking for an 80-bit floating point > value. > Im explicitly trying to import a call from C through the clang-importer (to ensure that long doubles are imported correctly). As such, unfortunately, I don't

Re: [swift-dev] long double usage in swift

Why not? https://github.com/apple/swift/blob/8d9ef80304d7b36e13619ea50e6e76f3ec9221ba/test/Inputs/clang-importer-sdk/usr/include/ctypes.h#L146 > On 23 Mar 2016, at 21:29, Saleem Abdulrasool wrote: > > On Wed, Mar 23, 2016 at 2:28 PM, Alex Blewitt > wrote: > There

Re: [swift-dev] long double usage in swift

On Wed, Mar 23, 2016 at 2:35 PM, Alex Blewitt wrote: > Why not? > > > https://github.com/apple/swift/blob/8d9ef80304d7b36e13619ea50e6e76f3ec9221ba/test/Inputs/clang-importer-sdk/usr/include/ctypes.h#L146 > AIUI, Float80 isn't exactly applicable to this test (since I want an explicit long double

Re: [swift-dev] long double usage in swift

> On Mar 23, 2016, at 2:25 PM, Saleem Abdulrasool via swift-dev > wrote: > > Hi, > > I was looking at an ABI related issue on Windows. In trying to construct a > test case, it seems that I am unable to import a declaration using a long > double into swift. I was wondering if there is somet

[swift-dev] [WIP] New pull request triggers

I am currently working on adding new pull request triggers to ci.swift.org, you might have already seen few of them as we test them out. Following phrases for apple/swift.git will be added: Benchmark Phrase: @swift-ci Please benchmark Description: Benchmark job will compare the results between

Re: [swift-dev] [WIP] New pull request triggers

> On Mar 23, 2016, at 4:26 PM, Mishal Shah via swift-dev > wrote: > > I am currently working on adding new pull request triggers to ci.swift.org > , you might have already seen few of them as we test > them out. This is really exciting... > Following phrases for apple

Re: [swift-dev] [WIP] New pull request triggers

> On Mar 23, 2016, at 5:01 PM, Andrew Trick wrote: > >> >> On Mar 23, 2016, at 4:26 PM, Mishal Shah via swift-dev > > wrote: >> >> I am currently working on adding new pull request triggers to ci.swift.org >> , you might have already seen few

Re: [swift-dev] long double usage in swift

On Wed, Mar 23, 2016 at 3:54 PM, Joe Groff wrote: > > > On Mar 23, 2016, at 2:25 PM, Saleem Abdulrasool via swift-dev < > swift-dev@swift.org> wrote: > > > > Hi, > > > > I was looking at an ABI related issue on Windows. In trying to > construct a test case, it seems that I am unable to import a

Re: [swift-dev] [WIP] New pull request triggers

> On Mar 23, 2016, at 5:21 PM, Mishal Shah wrote: > >> Will the smoke tests cover everything run by the incremental builders? > It will be covered by preset buildbot_incremental,tools=RA,stdlib=RA > Ok. That makes sense. I see that the build preset also invokes the tests, but that the increme