Post closed tickets in your report. | Note: This channel is for our weekly status meetings (Tuesdays at 19:30 UTC); you probably want #parrot instead. | irclog: irclog.perlgeek.de/
Set by moderator on 28 November 2013.
07:39 denis_boyun joined 08:56 lizmat joined 09:19 lizmat_ joined 13:10 denis_boyun joined 13:18 denis_boyun joined 14:43 bluescreen joined 17:08 denis_boyun joined 17:16 lizmat joined 18:51 lizmat joined
Util # Done: 19:34
* Nil (Holiday travel and such)
# Doing (Spilled from prior weeks):
* Update Zefram tickets with emailed rebuttals.
* Update GH#1016 with more detail.
* Testing and coordinating GH#1027.
.end
Hello! Who all are in attendance? 19:35
sa1 Hello Util
Util Hello, sa1.
sa1 I've been meaning to find something to work on too.
As I mentioned last week. 19:36
Util Do you have any threading or concurrency expertise?
sa1 Not much. I've read up on STM, as used in Haskell. 19:37
but not much with real life C/C++ projects.
Util have you read github.com/parrot/parrot/pull/1027 ?
19:37 denis_boyun joined
sa1 no, let me look at it. 19:38
Yes, caches can be troublesome with caches, but exactly how, depends on the code. Most code is single-threaded after all. 19:41
But no, I probably don't have as much knowledge as benabik about it. 19:42
Util We may need a threading specialist to write code to try to deliberately break the patch, or to tweak it. 19:45
In the meantime, it would be helpful if someone wrote step-by-step instructions to build
rakudo with the current Parrot patched with #1027, so that we can all try the Roast tests on different platforms and look for problems.
Interested?
sa1 How would it be different than building rakudo otherwise? 19:47
Its just a patched parrot?
Util Yes, but the instructions included with Rakudo point you toward either auto-building parrot using Rakudo's Configure.pl with the right flag, or 19:48
assumes you already have parrot built the way you like it, and then use Rakudo's Configure.pl to point to the pre-built Parrot. 19:49
sa1 ok, I will do this first thing in the morning.
Util If we want the Rakudo team to get in on the testing, we need to make it easy for them. Many of them don't ever build Parrot by itself anymore. 19:50
sa1++
sa1 However I need something to keep me busy for the vacation. Are you mostly free this winter? Or I can ask Duke again if he's free to mentor me on anything else. 19:52
Util sa1: I am more clear in December, but am bidding on a contract that might change that. Also, I have a 1.5-week on-site commitment mid-January. 19:54
Is there a project that you have your eye on already?
sa1 I wanted to learn about and help with the garbage collector. 19:56
Nothing is mentioned much in the Soc wiki and I'm not sure which part of the codebase you are most acquainted with. 19:58
Util I don't know what the next vacation-sized chunck of work is for the GC system. I will look, but you should also contact dukeleto about GC, and to see if he has anything else that would interest you. 19:59
Myself and GC: I had been studying the Garbage Collection Handbook early this year, and got about halfway through the book, but have not actually touched *Parrot's* GC yet. 20:00
sa1 Yeah, and advanced GC features might take more time to get right. 20:01
But I'll ask him too. 20:02
Util Great!
(for sa1 *and* lurkers) I do not see us getting #1027 in before the 5.11 release, 20:03
and it should not go into 6.0 (because it is a "stable" release), so I am targeting 6.1.0,
which should give us plenty of time to be thorough about this "might be broken for threads" issue.
20:06 bluescreen_ joined
Util sa1: congrats on completing your finals! 20:06
sa1 Ha! Thank you! :)
Util Does anyone have anything else to discuss, before we adjourn? 20:07
sa1 Not anything else from me.
Util++ 20:09
for all the help
Util :^)
OK then.
Meeting adjourned.
21:11 lizmat joined 23:46 lizmat joined 23:48 lizmat joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!