Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
Am Mon, 17 Jun 2013 22:03:09 +0200 schrieb "Joseph Rushton Wakeling" : > On Monday, 17 June 2013 at 15:19:27 UTC, Andrej Mitrovic wrote: > > There seems to be some audio glitching every couple of seconds > > (at the > > beginning). I've noticed this in other videos as well. It's > > mostly > > minimal though, not much harm done. > > https://www.youtube.com/watch?v=m6jsXQm5IrM#t=106s :-) "What's this wire doing here? It's dangerous!" *pulls* -- Marco
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On Mon, 17 Jun 2013 08:25:50 -0400 Andrei Alexandrescu wrote: > You know the drill! > > reddit: > http://www.reddit.com/r/programming/comments/1gie4b/dconf_2013_ldc_the_llvmbased_d_compiler_by_david/ > > hackernews: https://news.ycombinator.com/item?id=5892652 > > facebook: https://www.facebook.com/dlang.org/posts/658638807483137 > > twitter: https://twitter.com/D_Programming/status/346598441230671873 > > youtube: http://youtube.com/watch?v=ntdKZWSiJdY > > > Andrei Torrents/links up: http://semitwist.com/download/misc/dconf2013/
Re: DConf 2013 Day 3 Talk 2: Code Analysis for D with AnalyzeD by Stefan Rohe
On 2013-06-17 16:21, Steven Schveighoffer wrote: No, currently RTInfo is for types only. I want to have it work for modules as well (where unit tests typically live). I think I understand what you mean now. -- /Jacob Carlborg
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On Monday, 17 June 2013 at 15:19:27 UTC, Andrej Mitrovic wrote: There seems to be some audio glitching every couple of seconds (at the beginning). I've noticed this in other videos as well. It's mostly minimal though, not much harm done. https://www.youtube.com/watch?v=m6jsXQm5IrM#t=106s :-)
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On Monday, 17 June 2013 at 15:56:21 UTC, Justin Whear wrote: On Mon, 17 Jun 2013 17:41:22 +0200, nazriel wrote: On Monday, 17 June 2013 at 13:47:20 UTC, bearophile wrote: Andrei Alexandrescu: http://www.reddit.com/r/programming/comments/1gie4b/ dconf_2013_ldc_the_llvmbased_d_compiler_by_david/ Slide 14: PFFT (SSE) seems slow on LDC2: if you can extract a small test case LLVM devs will appreciate a lot a bug report (they fixed many lacks of optimizations submitted by me). If you have a link to the PFFT code them maybe I can do that myself. I don't know what PFFT stands for (can't google it either, funny results shows up) but if it related to vectorization then maybe LDC has been slower because it was built against LLVM 3.3 while LLVM 3.4 brings more vector optimizations. Maybe all what has to be done, is rerunning benchmarks against LDC + LLVM 3.4 ? Slide 25: Implicit invariants often hard to track down Then maybe it's a good idea to add such invariants to the dmd front-end code, even before its port to D. Bye, bearophile My guess is Parallel Fast Fourier Transform. It's Pretty Fast Fourier Transform. The code is at https://github.com/jerro/pfft/tree/experimental (I linked to the experimental branch because master branch is quite outdated)
Re: DConf 2013 Day 3 Talk 1: Metaprogramming in the Real World by Don Clugston
Jacob Carlborg, el 17 de June a las 12:42 me escribiste: > On 2013-06-17 10:39, Regan Heath wrote: > > >Oh, yes, the ability to capture the compiler output and do a bit of a > >parse and jump to error is another top IDE feature IMO. > > I have that in TextMate :) Same in VIM. -- Leandro Lucarella (AKA luca) http://llucax.com.ar/ -- GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05) -- You can try the best you can If you try the best you can The best you can is good enough
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On 6/17/2013 8:35 AM, Steven Schveighoffer wrote: I'm sure if there are any glitches that omit an important piece of the talk, point them out and the speaker and/or conference attendees can help discern what was being said. I was saying "flip that!".
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On 6/17/13 8:25 AM, Andrei Alexandrescu wrote: You know the drill! reddit: http://www.reddit.com/r/programming/comments/1gie4b/dconf_2013_ldc_the_llvmbased_d_compiler_by_david/ hackernews: https://news.ycombinator.com/item?id=5892652 facebook: https://www.facebook.com/dlang.org/posts/658638807483137 twitter: https://twitter.com/D_Programming/status/346598441230671873 youtube: http://youtube.com/watch?v=ntdKZWSiJdY Andrei HD video up: https://archive.org/details/dconf2013-day03-talk04 Andrei
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On Mon, 17 Jun 2013 17:41:22 +0200, nazriel wrote: > On Monday, 17 June 2013 at 13:47:20 UTC, bearophile wrote: >> Andrei Alexandrescu: >> >>> http://www.reddit.com/r/programming/comments/1gie4b/ dconf_2013_ldc_the_llvmbased_d_compiler_by_david/ >> >> Slide 14: >> >> PFFT (SSE) seems slow on LDC2: if you can extract a small test case >> LLVM devs will appreciate a lot a bug report (they fixed many lacks of >> optimizations submitted by me). If you have a link to the PFFT code >> them maybe I can do that myself. >> > I don't know what PFFT stands for (can't google it either, funny results > shows up) but if it related to vectorization then maybe LDC has been > slower because it was built against LLVM 3.3 while LLVM 3.4 brings more > vector optimizations. > > Maybe all what has to be done, is rerunning benchmarks against LDC + > LLVM 3.4 ? >> >> Slide 25: >>> Implicit invariants often hard to track down >> >> Then maybe it's a good idea to add such invariants to the dmd front-end >> code, even before its port to D. >> >> Bye, >> bearophile My guess is Parallel Fast Fourier Transform.
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On Monday, 17 June 2013 at 13:47:20 UTC, bearophile wrote: Andrei Alexandrescu: http://www.reddit.com/r/programming/comments/1gie4b/dconf_2013_ldc_the_llvmbased_d_compiler_by_david/ Slide 14: PFFT (SSE) seems slow on LDC2: if you can extract a small test case LLVM devs will appreciate a lot a bug report (they fixed many lacks of optimizations submitted by me). If you have a link to the PFFT code them maybe I can do that myself. I don't know what PFFT stands for (can't google it either, funny results shows up) but if it related to vectorization then maybe LDC has been slower because it was built against LLVM 3.3 while LLVM 3.4 brings more vector optimizations. Maybe all what has to be done, is rerunning benchmarks against LDC + LLVM 3.4 ? Slide 25: Implicit invariants often hard to track down Then maybe it's a good idea to add such invariants to the dmd front-end code, even before its port to D. Bye, bearophile
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On Mon, 17 Jun 2013 11:19:14 -0400, Andrej Mitrovic wrote: On 6/17/13, Andrei Alexandrescu wrote: youtube: http://youtube.com/watch?v=ntdKZWSiJdY There seems to be some audio glitching every couple of seconds (at the beginning). I've noticed this in other videos as well. It's mostly minimal though, not much harm done. I noticed that during the conference. There were several talks where the mic was giving the AV guys trouble. Each of the speakers was using a clip-on remote mic. Of course, live, it wasn't as big a deal, as we could hear the person talking :) But it would be more glaring for the recording. I'm sure if there are any glitches that omit an important piece of the talk, point them out and the speaker and/or conference attendees can help discern what was being said. -Steve
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
On 6/17/13, Andrei Alexandrescu wrote: > youtube: http://youtube.com/watch?v=ntdKZWSiJdY There seems to be some audio glitching every couple of seconds (at the beginning). I've noticed this in other videos as well. It's mostly minimal though, not much harm done.
Re: DConf 2013 Day 3 Talk 2: Code Analysis for D with AnalyzeD by Stefan Rohe
On Sat, 15 Jun 2013 11:16:22 -0400, Jacob Carlborg wrote: On 2013-06-14 17:13, Steven Schveighoffer wrote: With @UDAs, we have a lot of unrealized power for unit tests. I have asked for ModuleInfo to contain an rtInfo member [1], like TypeInfo does. With that, and possibly splitting the unit tests into individual functions (if not done already, I don't know), you have all you need to completely re-design the unit testing framework. It can even be runtime selectable. It would also be nice to not have to change the druntime to use RTInfo. Is that part of what you're suggesting? No, currently RTInfo is for types only. I want to have it work for modules as well (where unit tests typically live). It would be nice to make it easily extensible. I think that can be done by keying on certain members in the type/module. -Steve
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
Andrei Alexandrescu: http://www.reddit.com/r/programming/comments/1gie4b/dconf_2013_ldc_the_llvmbased_d_compiler_by_david/ Slide 14: PFFT (SSE) seems slow on LDC2: if you can extract a small test case LLVM devs will appreciate a lot a bug report (they fixed many lacks of optimizations submitted by me). If you have a link to the PFFT code them maybe I can do that myself. Slide 25: Implicit invariants often hard to track down Then maybe it's a good idea to add such invariants to the dmd front-end code, even before its port to D. Bye, bearophile
Re: DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
Great talk! Regarding the ci.lycus.org fleet, credit should definitely go to Adam Wilson (C# to D talk) and Kelly Wilson (same person who was present in the pie chart) too for providing many of the machines hooked up to the master node. The fleet doesn't do a whole lot of work most of the time, so if you have a project that 1) has a sane build system; 2) you're willing to respond to build failures on; 3) and is 'significant' enough, feel free to email me and I'll see what I can do. (By 'significant' I mean "has enough impact to be useful for a reasonable amount of D programmers". This is of course pretty subjective, but we have to be a bit conservative about how many projects we add so that we don't end up having lots of stalled builds in the queue.)
DConf 2013 Day 3 Talk 4: LDC by David Nadlinger
You know the drill! reddit: http://www.reddit.com/r/programming/comments/1gie4b/dconf_2013_ldc_the_llvmbased_d_compiler_by_david/ hackernews: https://news.ycombinator.com/item?id=5892652 facebook: https://www.facebook.com/dlang.org/posts/658638807483137 twitter: https://twitter.com/D_Programming/status/346598441230671873 youtube: http://youtube.com/watch?v=ntdKZWSiJdY Andrei
Re: DConf 2013 Day 3 Talk 1: Metaprogramming in the Real World by Don Clugston
On 2013-06-17 10:39, Regan Heath wrote: Oh, yes, the ability to capture the compiler output and do a bit of a parse and jump to error is another top IDE feature IMO. I have that in TextMate :) -- /Jacob Carlborg
Re: DConf 2013 Day 3 Talk 1: Metaprogramming in the Real World by Don Clugston
On Fri, 14 Jun 2013 23:34:56 +0100, Nick Sabalausky wrote: "click an error to jump to it's line in the source". Is there a hotkey for this? .. it's little things like having a configurable hotkey (so I can make it F4 like in MSVC that make or break a new IDE/editor IMO). R -- Using Opera's revolutionary email client: http://www.opera.com/mail/
Re: DConf 2013 Day 3 Talk 1: Metaprogramming in the Real World by Don Clugston
On Fri, 14 Jun 2013 23:34:56 +0100, Nick Sabalausky wrote: On Thu, 13 Jun 2013 11:48:52 +0100 "Regan Heath" wrote: I use Notepad++ now and have used TextPad in the past. But, those are just text editors with syntax highlighting (fairly flexibly and simply customisable highlighting BTW). What are the basic features you would require of a development environment, I am thinking of features which go beyond the basic concept of a text editor, such as: - The concept of a 'project' or some other collection of source files which can be loaded/displayed in some fashion to make it easier to find/select/edit individual files - The ability to hook in 'tools' to key presses like "compile" executing "dmd ..." or similar. I've been using Programmer's Notepad 2 (for *all* my development for the past few years), which is *mostly* a syntax highlighting editor, but also has a concept of projects, configurable tools, and "click an error to jump to it's line in the source". And I've never had it crash or get wonky, or slowdown, or stall, or use a lot of resources, ever. Oh, yes, the ability to capture the compiler output and do a bit of a parse and jump to error is another top IDE feature IMO. R -- Using Opera's revolutionary email client: http://www.opera.com/mail/
