p again and
> see if it shows up.
>
> Thanks!
>
> Ben
>
> On Thu, Dec 1, 2016 at 7:10 PM, Ben Asher wrote:
>
>> Sure thing! I’ll see if I can put small reproducers together tomorrow.
>>
>> Ben
>>
>> On Thu, Dec 1, 2016 at 7:08 PM, Mark Lacey w
Lacey wrote:
>
>>
>> On Dec 1, 2016, at 5:48 PM, Ben Asher via swift-dev
>> wrote:
>>
>> The build failed compiling 3 files in our project. Our app is crashing
>> that snapshot; here is some output from the failures:
>>
>>
>> It would be
Sure thing! I’ll see if I can put small reproducers together tomorrow.
Ben
On Thu, Dec 1, 2016 at 7:08 PM, Mark Lacey wrote:
>
> On Dec 1, 2016, at 5:48 PM, Ben Asher via swift-dev
> wrote:
>
> The build failed compiling 3 files in our project. Our app is crashing
> that
> Here's an example of what this method looks like:
>
> + (NSSet *)setWithSELs:(SEL[])sels count:(NSUInteger)count;
>
> Could this point to more duplicated work?
>
> Ben
>
> On Thu, Dec 1, 2016 at 2:50 PM, Ben Asher wrote:
>
>> Sure! Thanks for reminding m
wrote:
> Sure! Thanks for reminding me. I'll follow up on that, test, and get back
> to you.
>
> Ben
>
> On Thu, Dec 1, 2016 at 2:48 PM, Mark Lacey wrote:
>
>>
>> On Dec 1, 2016, at 3:13 PM, Ben Asher via swift-dev
>> wrote:
>>
>> Just
Sure! Thanks for reminding me. I'll follow up on that, test, and get back
to you.
Ben
On Thu, Dec 1, 2016 at 2:48 PM, Mark Lacey wrote:
>
> On Dec 1, 2016, at 3:13 PM, Ben Asher via swift-dev
> wrote:
>
> Just running a quick trial before and after I made this change in ou
to work to make this drastic speed difference go away, so if
>> you're able we (at Apple) would love to have a source drop of your Swift 3
>> project, for additional data on where the problems are. Mind filing a Radar?
>>
>> Best,
>> Jordan
>>
>>
>
o away, so if
> you're able we (at Apple) would love to have a source drop of your Swift 3
> project, for additional data on where the problems are. Mind filing a Radar?
>
> Best,
> Jordan
>
>
> > On Dec 1, 2016, at 11:51, Ben Asher via swift-dev
> wrote:
> >
Hello! Someone recently tipped me off to using -whole-module-optimization
flag with -Onone for use during debug builds to speed up compile times. In
our project, the speedup feels quite dramatic, but when it gets to the
linking step (after compiling both Swift and Obj-C in the project) it fails
bec
This is awesome. Thanks Graydon!!
Ben
On Wed, Nov 2, 2016 at 6:43 PM, Graydon Hoare via swift-dev <
swift-dev@swift.org> wrote:
> Hi,
>
> I've been working a bit on testing infrastructure for systematically
> improving swiftc compilation performance. Attached is a document
> summarizing both the
r this, but I suspect
>>>> ConstraintSystem::solve()
>>>> might be the best. This is ultimately called from a variety of places, and
>>>> would provide the most insight into where time is being spent in the
>>>> expression type checking. It’s possible
cking for some help on getting started. I’ll
>>> probably try to add this timer myself in the next few weeks if you don’t
>>> manage to beat me to it.
>>>
>>> Mark
>>>
>>>
>>> I don't mind building from Swift master, using someone
lf in the next few weeks if you don’t
>> manage to beat me to it.
>>
>> Mark
>>
>>
>> I don't mind building from Swift master, using someone's preferred
>> profiling tools, etc. I'm not really sure where to start.
>>
>> Ben
>>
8.0 (from the App Store).
>>
>> I'll try with Xcode 8.1 beta this afternoon and report back. Ill also
>> open a ticket for improving -debug-time-function-bodies if I can confirm
>> anything.
>>
>> Thanks!
>>
>> Ben
>>
>> On Wed, Oct 5, 2016 at 1
12.0),
> Xcode 8.0 (from the App Store).
>
> I'll try with Xcode 8.1 beta this afternoon and report back. Ill also open
> a ticket for improving -debug-time-function-bodies if I can confirm
> anything.
>
> Thanks!
>
> Ben
>
> On Wed, Oct 5, 2016 at 1:00 PM, Ma
at 1:00 PM, Mark Lacey wrote:
>
> On Oct 4, 2016, at 2:38 PM, Ben Asher via swift-dev
> wrote:
>
> Hello! I work with a large project (~900 .swift files and more .m files).
> We have a nightly job that compiles the app and calls out function bodies
> (using -debug-time
ur team's use case sounds very similar to his, so I'd
> encourage you to chime in on that issue with your thoughts.
>
> - Brian Gesiak
>
>
> On Tue, Oct 4, 2016 at 5:38 PM, Ben Asher via swift-dev <
> swift-dev@swift.org> wrote:
>
>> Hello! I work with a
Hello! I work with a large project (~900 .swift files and more .m files).
We have a nightly job that compiles the app and calls out function bodies
(using -debug-time-function-bodies) that are slower than 100ms to compile.
Since upgrading to Swift 3, the number of trouble function bodies has one
fr
18 matches
Mail list logo
