|
Parrot 3.8.0 "Magrathea" | parrot.org | Log: irclog.perlgeek.de/parrot | #parrotsketch meeting Tuesday 19:30 UTC Set by moderator on 29 September 2011. |
|||
| dukeleto | cotto: do you see yourself working on m0 much before the next release? | 00:05 | |
|
00:25
l3l1p joined
02:37
rfw joined
02:52
dngor joined
|
|||
| cotto | dukeleto, yes | 03:33 | |
| dukeleto | cotto: what are the priorities? finish the C implementation? | 03:41 | |
| tadzik | hello parrots | 03:42 | |
| cotto | dukeleto, 1) compare x86, x64, arm and possibly mips 2) expand the number of ops in the perl5 implementation so they map ~cleanly to the capabilities of those CPUs 3) make the same changes to the C implementaiton | 03:45 | |
|
04:59
l3l1p joined
05:08
perlite_ joined
05:37
contingencyplan joined
05:42
l3l1p joined
06:37
nbrown joined
07:16
baest joined
07:19
SHODAN joined
08:02
lucian joined
|
|||
| lucian | Coke: pick Java for what? | 09:52 | |
| lucian waves, belatedly | 09:53 | ||
|
10:09
lateau__ joined
|
|||
| dalek | kudo/nom: abc6874 | moritz++ | src/Perl6/Metamodel/C3MRO.pm: fix c3 MRO, patch by mls++ |
10:53 | |
|
11:37
Psyche^ joined
|
|||
| dalek | p: fbe7f0b | mls++ | src/how/NQPClassHOW.pm: backport C3 fix from rakudo |
11:52 | |
|
12:17
mtk joined
12:22
preflex_ joined
12:27
whiteknight joined
|
|||
| whiteknight | good morning, #parrot | 12:27 | |
|
12:35
Coke joined
|
|||
| dalek | kudo/nom: 38907e7 | moritz++ | src/core/Match.pm: improve Match.gist for failed matches. Also correct Match.perl, masak++ |
12:52 | |
|
12:55
jjore joined
13:32
SHODAN joined
13:45
PacoLinux joined
14:33
contingencyplan joined
14:37
nbrown joined
|
|||
| dalek | rrot: 08a15fc | gerd++ | / (14 files): change struct name form "Buffer" to "Parrot_Buffer" to avoid name conflicts |
14:40 | |
| dukeleto | ~~ | 14:53 | |
|
15:09
mtk joined
15:16
dmalcolm joined
15:28
bluescreen joined,
bluescreen_ joined
|
|||
| dukeleto | github.com/parrot/parrot/wiki/Overview is quite nice | 15:57 | |
| Why does parrot.git contain AIX assembly? github.com/parrot/parrot/blob/mast.../aix/asm.s | 16:08 | ||
| does parrot even build on AIX? | |||
| dalek | rrot: 537d8e7 | dukeleto++ | ChangeLog: Add more to the changelog |
16:12 | |
| rrot: b79de3a | dukeleto++ | src/platform/aix/asm.s: Remove some jit remnants from our AIX assembly(!) |
|||
| whiteknight | dukeleto: may have at one time | 16:13 | |
| I can't test it, so I can't say for sure | 16:14 | ||
| dukeleto | whiteknight: it would be interesting to see how it fares. Perhaps we can ask the p5p people to test it | ||
| PacoLinux | I compiled parrot in aix time ago .. | ||
| dukeleto | whiteknight: if AIX is not a supported platform, should we still have aix assembly in our repo? | ||
| PacoLinux: interesting! | |||
| PacoLinux | (and worked fine) | 16:15 | |
| dukeleto | PacoLinux: how long ago? were you able to run "make smoke" ? | ||
| PacoLinux | 1 year and a half, and yes, i think to remember smoke worked | 16:16 | |
| dukeleto | whiteknight: i have been under a rock a bit. Has there been any movement on whether we have a deprecation policy any more? | ||
| mls: how does one use the new subprof runcore? Are there docs somewhere? | 16:17 | ||
| Also, can somebody tell me exactly what github.com/parrot/parrot/blob/mast...ia64/asm.s does ? | 16:18 | ||
| that code could benefit from a comment or two | 16:19 | ||
| PacoLinux | back in time, I compiled parrot in exotic oses, like irix, solaris(sparc), openvms(alpha) and aix | ||
| dalek | rrot: b725c3f | dukeleto++ | ChangeLog: Add note about share/share_ro vtables being gone to the changelog |
16:23 | |
| dukeleto | PacoLinux: do you still have access to some of those machines? | ||
| PacoLinux | yes | 16:37 | |
| dukeleto | PacoLinux: it would be very interesting to see if Parrot still compiles and tests ok on aix, if you have spare time | 16:38 | |
| PacoLinux | I will try in other moment | 16:39 | |
| dukeleto | PacoLinux: thanks! | 16:43 | |
| parrot-dev has been eerily quiet lately | |||
| PacoLinux | dukeleto: :) | 16:44 | |
|
16:46
fperrad joined
17:16
gbacon joined
|
|||
| dalek | Heuristic branch merge: pushed 22 commits to rakudo/optimizer by moritz | 17:40 | |
| cotto | ~~ | 17:47 | |
| whiteknight | dukeleto: As far as I am concerned, I am acting as if there is no deprecation policy anymore | ||
| dukeleto: I | |||
| m replacing it with a general attitude of trying to do things with intelligent well-being for the good of Rakudo | 17:48 | ||
| dukeleto | whiteknight: ok, i like it. I am trying to think up stuff to write in our changelog | 17:59 | |
|
18:01
benabik joined
|
|||
| whiteknight | ok | 18:05 | |
| benabik | o/ #parrot | ||
| mls | dukeleto: simply run parrot with -R subprof | ||
| dukeleto | mls: awesome, thanks | 18:06 | |
| mls | currently it writes the profiling output to stdout | ||
| when parrot is done, run kcachegrind on the data | |||
| dukeleto | mls: do we have this written down somewhere? It sounds perfect for our new github wiki | 18:07 | |
| mls | (there's also the somewhat hidden -R subprof_sub and -R subprof_ops. sub records data on a subroutine level, ops does it on opcode level) | ||
| benabik | mls: What does it profile at by default? | ||
| mls | the default is subprof_hll, i.e. "annotation block" level | 18:08 | |
| benabik | Annotation block? By HLL line? | ||
| mls | yes | 18:09 | |
| dalek | rrot: 5941717 | dukeleto++ | ChangeLog: Add note about how to use the profile runcore |
||
| benabik | Neat. | ||
| mls | afk -> home | 18:13 | |
| Coke | (new github wiki) what? | 18:25 | |
| benabik | Coke: github.com/parrot/parrot/wiki | ||
| soh_cah_toa did a lot of cleaning up of stuff from the old wiki, which is a bit of a mess. | 18:26 | ||
| Coke | yes, I know how to /get/ there. when did we start using that? | ||
| whiteknight | there wasn't any discussion about it, if that's what you're asking | 18:27 | |
| Coke | (I don't see anything on parrot-dev matching "github wiki" after May 13th, and it's not about the github wiki. | ||
| whiteknight | soh_cah_toa started playing with it, it's not an official thing yet | ||
| but, if the results are looking good, we might start talking about it more seriously | 18:28 | ||
| Coke | Ok. for people who are not following every send in IRC, (and in the logs, since netsplits), pinging things like that to the dev list would probably be a good idea. | ||
| cotto | yes | ||
| benabik | There was a little bit of talk. soh_cah_toa said he had been cleaning up wiki-info into his github fork. Someone else told him "just put it in the parrot one. | ||
| cotto | <-- | ||
| whiteknight | Coke: It's really nothing to talk about yet. It's just an experiment | 18:29 | |
| Coke | please forget I mentioned it. | 18:31 | |
| benabik | Coke: No, you have a good point about mentioning things on -dev. I tend to forget about it sometimes. :-/ | ||
| whiteknight | I wasn't under the impression that it was in a state yet worth mentioning on parrot-dev | 18:38 | |
| I may be outdated | |||
|
18:39
dngor joined
18:40
PacoLinux_ joined
|
|||
| Coke | whiteknight: what's the plan, then: wait until it's ready to replace the existing wiki before mentioning it? | 18:45 | |
| (wrong order.) | 18:46 | ||
| if it's intended to supplement, not replace, why duplicate effort in the meantime. What about people who find the wiki on github and never see trac? ... | |||
|
18:56
bluescreen joined
18:58
alester joined
|
|||
| dukeleto | Coke: i just sent an email to parrot-dev to spark discussion (as I am wont to do) | 18:59 | |
|
19:04
logie joined
|
|||
| whiteknight | Coke: There is no plan that I am aware of. It's not my project, it's soh_cah_toa's. | 19:11 | |
|
19:26
preflex_ joined
|
|||
| nine | Good evening. I got green_threads working, passing fulltest and Rakudo's spectest. So what's the next step? | 19:45 | |
| benabik | nine: We hold a party for you, I think. :-D | 19:46 | |
| Coke | nine - like, I can spawn threads and have them do things? | 19:47 | |
| cotto | nine: send a writeup to parrot-dev about what's possible now and what we can do to get a more complete implementation. | ||
| nine++ | 19:48 | ||
| nine | Coke: tasks :) which will run concurrently to the main task as long as you don't do any blocking I/O | ||
| Coke: but it's a start | |||
| Coke | nine++! | ||
| I'd love to get that working with auto-threading in rakudo! | |||
| whiteknight | nine: if Parrot passes all tests and if Rakudo builds fine, we want to start talking merge and integrate | 19:49 | |
| nine | :) | 19:50 | |
| So I'll write up something tomorrow | |||
| whiteknight | that's the substrate we are going to want to build on top of | 19:51 | |
| Coke | nine: you tested "nom" branch on rakudo, yes? | 19:54 | |
| nine | Apart from some small optimizations the next step will probably be to introduce real threads into the mix | ||
| And at the same time start thinking about how to use these features in Rakudo and Perl 6. Because from what I've seen here those past months, such things really shouldn't be developed without some serious communications with Rakudo folk | 19:56 | ||
| moritz | +Inf to that :-) | ||
| cotto | +1 | 20:01 | |
| nine | cotto: yes, I tested nom | 20:02 | |
| Coke: yes, I tested nom | 20:03 | ||
| Coke | excellent. | ||
| cotto | nine: great | 20:10 | |
| nine: big bonus points if you show some code that can't be done without the changes in green_threads | 20:11 | ||
| nine | To be fair: most of what's in green_threads comes from gsoc_threads. I just cleaned it up and fixed a couple of things. | 20:12 | |
| Off to bed now | |||
| whiteknight | yeah, we are definitely going to have to explore this branch now, make sure the new stuff is well tested, and talk merge to master | 20:17 | |
| all it provides is a preemptive green threads implementation, and one that is hampered by other design issues in Parrot (nested runloops,etc), so it's a good start but it something we need to build up from | 20:18 | ||
| dukeleto | +1 to iterative improvement | 20:19 | |
| whiteknight | what's most important, and I've been saying this for a while, is that we start getting the interface into place so that we can start getting users acclimated to it and start generating feedback | 20:20 | |
| until we get blocking IO sorted out on the branch, it's not going to provide any performance improvements, yet | 20:21 | ||
|
20:29
rfw joined
21:28
Coke joined
21:37
jsut_ joined
22:27
soh_cah_toa joined
23:12
whiteknight joined
|
|||
| dalek | rrot: ea2a265 | jkeenan++ | RESPONSIBLE_PARTIES: Update role. |
23:15 | |
| cotto | sad face | 23:23 | |
| dalek | rrot: 0889a4a | jkeenan++ | src/gc/gc_gms.c: [codingstd] Break line so it meets the linelength limitation. |
23:46 | |
| rrot: 5f8ff5d | jkeenan++ | src/ (8 files): [codingstd] gerd++ reported failures in c_function_docs.t. These can be signatures in POD back into line with revised signatures in the functions themselves. |
|||