Re: Five Projects Selected for SAOC 2019
On Tuesday, 27 August 2019 at 17:11:33 UTC, Mike Franklin wrote: If you look at the vibe.d compile-time graph, you'll see there's a 2.5s increase around Mid-2014. Sorry, that should be Mid-2015.
Re: Silicon Valley C++ Meetup - August 28, 2019 - "C++ vs D: Let the Battle Commence"
On Tue, Aug 27, 2019 at 12:25 PM Ali Çehreli via Digitalmars-d-announce wrote: > > I will be presenting a comparison of D and C++. RSVP so that we know how > much food to order: > >https://www.meetup.com/ACCU-Bay-Area/events/263679081/ > > It will not be streamed live but some people want to record it; so, it > may appear on YouTube soon. > > As always, I have way too many slides. :) The contents are > > - Introduction > - Generative programming with D > - Thousand cuts of D > - C++ vs. D > - Soapboxing > > Ali Wednesday? :( I briefly pondered skipping up for the weekend...
Silicon Valley C++ Meetup - August 28, 2019 - "C++ vs D: Let the Battle Commence"
I will be presenting a comparison of D and C++. RSVP so that we know how much food to order: https://www.meetup.com/ACCU-Bay-Area/events/263679081/ It will not be streamed live but some people want to record it; so, it may appear on YouTube soon. As always, I have way too many slides. :) The contents are - Introduction - Generative programming with D - Thousand cuts of D - C++ vs. D - Soapboxing Ali
Re: Five Projects Selected for SAOC 2019
On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev wrote: On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote: The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog: https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/ Sorry, I haven't been following. Don't we already have an implementation of the "Create a CI or other infrastructure for measuring D’s progress and performance" project? I just haven't been maintaining it because there hasn't been a lot of interest in it while it was being maintained. Here's the original blog post: https://blog.thecybershadow.net/2015/05/05/is-d-slim-yet/ I'll give it a kick and get it back online if there is interest. Seems wasteful to reimplement it from scratch, though. I was aware of the site when i wrote the proposal, but the idea is to create the infrastructure to add more measurements too, e.g. profiling the compiler or testing it under limited memory (I found out how much memory my CTFE thing was using the other day!). Assuming I can get it to work I'd also like to throw the Linux perf system in there too, but As mentioned in the summary, this will extend to runtime performance too but that obviously raises the question of how to ensure consistent performance of the testing machine (or give a relative figure).
Re: Five Projects Selected for SAOC 2019
On Tuesday, 27 August 2019 at 14:42:28 UTC, Vladimir Panteleev wrote: On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev wrote: On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote: The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog: https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/ Sorry, I haven't been following. Don't we already have an implementation of the "Create a CI or other infrastructure for measuring D’s progress and performance" project? I just haven't been maintaining it because there hasn't been a lot of interest in it while it was being maintained. Max, if you're still excited about this project, please ping me on IRC or Slack. Would love to brainstorm with you and hear your ideas. Vladimir, I would love to (and I need to acquire a mentor, so if you're not busy... ;) ) but I am struggling to even load the forum (I'm on holiday) but I'll be back to civilisation within a day or two. To anyone else reading: If the gods allow it, I'm *trying* to answer questions about my proposal but my internet connection is genuinely shit ATM
Re: Five Projects Selected for SAOC 2019
On Tuesday, 27 August 2019 at 12:58:20 UTC, Vladimir Panteleev wrote: It will eventually zero in to commit-level accuracy after it's been running for a while. I cleared the database as the last time it was running, it was on another CPU, so the timings are going to be different. (Still need to decide on a way to measure execution time in some deterministic way.) If you look at the vibe.d compile-time graph, you'll see there's a 2.5s increase around Mid-2014. When I zoom in and visit the commit, it's just a DDoc comment change (https://github.com/dlang/phobos/pull/3542). I don't see how that could account for the large increase in compile time. Mike
Re: Five Projects Selected for SAOC 2019
On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev wrote: On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote: The Symmetry Autumn of Code 2019 application selection process has come to an end. This year, we've got five projects instead of three. Congratulations to everyone who was selected! You can read about them and their projects over at the D Blog: https://dlang.org/blog/2019/08/25/saoc-2019-projects-and-participants/ Sorry, I haven't been following. Don't we already have an implementation of the "Create a CI or other infrastructure for measuring D’s progress and performance" project? I just haven't been maintaining it because there hasn't been a lot of interest in it while it was being maintained. Max, if you're still excited about this project, please ping me on IRC or Slack. Would love to brainstorm with you and hear your ideas.
Re: Five Projects Selected for SAOC 2019
On Tuesday, 27 August 2019 at 09:08:58 UTC, Mike Franklin wrote: It's great to see this back up and running. The compile-time data is quite interesting. Is there any way to identify a particular offending commit. The commits identified in the data points on the chart don't seem to be precise. It will eventually zero in to commit-level accuracy after it's been running for a while. I cleared the database as the last time it was running, it was on another CPU, so the timings are going to be different. (Still need to decide on a way to measure execution time in some deterministic way.)
Re: Cross-compiling dub projects with LDC
Is this supports only in dub-1.17.0-beta.2 and it's not include to ldc2-1.17.0? It feature only in dub-master by now But it's cool works) Thanks!
Re: Cross-compiling dub projects with LDC
On Sunday, 25 August 2019 at 21:16:22 UTC, kinke wrote: The resulting cctest.exe (incl. 2 DLLs) can be copied to a Win64 box and then runs fine, as long as a Visual C++ runtime ≥ 2015 is installed. Tested on a Linux host, but should work on any host. Is this supports only in dub-1.17.0-beta.2 and it's not include to ldc2-1.17.0?
Re: Five Projects Selected for SAOC 2019
On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev wrote: Here's the original blog post: https://blog.thecybershadow.net/2015/05/05/is-d-slim-yet/ I'll give it a kick and get it back online if there is interest. Seems wasteful to reimplement it from scratch, though. It's great to see this back up and running. The compile-time data is quite interesting. Is there any way to identify a particular offending commit. The commits identified in the data points on the chart don't seem to be precise. Mike
