"Tuesday at 20:30 UTC"
Set by moderator on 2 June 2010.
00:39 darbelo joined 04:35 contingencyplan joined 04:36 contingencyplan joined 07:41 whiteknight joined 12:18 bluescreen joined 12:57 mikehh joined 17:46 cotto_work joined 18:37 Chandon joined 18:39 bubaflub joined 18:45 tewk joined 19:15 chromatic joined 19:20 khairul joined 20:00 NotFound joined 20:04 smash joined 20:06 tcurtis joined
mikehh What I did since my last report: 20:07
* building and testing parrot on amd64/i386, with gcc/g++
* various fixes
* branch testing and some fixes
* make corevm/make coretest is PASSing all tests again
* mainly due to efforts of plobsing++ and bacek++
* closed some related tickets and also TT #1135
* tested rakudo mainly but also partcl and partcl-nqp on various parrot builds
What I intend to do in the next week:
* testing and fixing
.eor
darbelo fails with EREPORTEDINTHEBLOG 20:08
tcurtis What I did:
All of the following except where specified otherwise are referring to the gsoc_past_optimization branch.
* Implemented :g/:global and :p/:pos attributes for matching PAST::Patterns.
* Implemented .transform method for PAST::Pattern. 20:09
* Added an example of constant folding with PAST::Pattern.
* Updated MANIFEST.generated.
* Wrote the beginning of a tutorial: 20:10
- parrot.org/content/adding-optimizat...astpattern
* Started working on documentation.
* Made a fork on NQP-rx for testing of my optimizations:
- github.com/ekiru/nqp-rx
What I will do:
* Fix any more bugs that are discovered.
EOR
20:11 plobsing_work joined
plobsing_work What I Did: 20:12
+ create dynop_mapping branch to deal with dynop/PBC issues
- selected approach: code segments get optables, mapping frozen in pbc
- made space available for frozen mappings in bytecode segments 20:13
- next steps: get IMCC to emit the mappings, renumber ops (requires IMCC to not emit ops immediately)
What I Plan:
+ continue with dynop_mapping fix
+ merge nci changes from ash when ready for a wider audience 20:14
EOR
tcurtis I'm failing at pasting my full report somehow(I blame line endings). nopaste.snit.ch/21271 for my full report.
Chandon Done:
* Discovered that Timers don't really work as advertised.
Will do:
* Write blog post.
* Make timers work in gsoc_threads branch.
khairul Did: 20:15
-added event notifications to runtime library
-added dynlib detection
-consolidated blog post for week 2 and 3 (parrot.mangkok.com/?p=106)
Will do:
-handle exit opcodes properly (Currently crashes)
-expose file/line info
-add more types of event notifications (per class, per sub, per method)
-tests for runtime library now that it is fairly fixed
EOR
NotFound What I did: 20:16
-parrot
* Created ByteBuffer PMC and its tests
* Implement a sane default for FIA sort method
* Refactor and improve embed tests
* Created the function Parrot_warn_deprecated
* Added a bunch of tests, guided by coverage results, and reformating
some PMC code to make it easier to cover. Located and fixed some bug
while doing that.
-winxed
* Backported pirops syntax to stage 0
* Stop using ParrotInterpreter stdhandle method, using pirops getstd... instead.
* Improved get_..._keyed type selection for generated code
* Implemented predef ord in stage 0 and moved ord and chr tests
to basic tests directory.
* Back to always expanding const strings, stop using .const pir directive
What I will do:
No plan. Probably adding more coverage improving tests.
EOR
cotto_work #did: 20:17
- helped khairul with some questions, did some code review
- OSUOSL should be setting up a git/trac test site within the next day or two
#will do:
- hack on git/trac
- Lorito cheerleading
- ?
#eor
Util # Done: 20:19
* Wrote Perl6book section on currying.
* Looked into unnecessary rebuilding of Rakudo during `make test`
= File::Copy on Win32 preserves timestamps; will change to ExtUtils::Command
# Plan to do:
* Fix Win32 Rakudo failure
* Attend YAPC
* Finish Top10 presentation.
# Blockers:
* $WORK
.end
Coke DID: 20:20
- parrot:
- wrote tests for parrot_config
- fixed tools/dev/pprof2cg.pl to give usage instead of explode.
- fix bug with non-ascii temp path.
- gut opcode listing from PDD 06.
- eliminate PARROT_NET_DEVEL
- ticket wrangling
TODO:
- parrot: - fix 'make html' issues (several TTs). (may involve substantial changes)
- partcl-nqp: - find out why new tests are failing. :( 20:21
- YAPC.
EOR
bubaflub Did:
* Parrot configures on RTEMS (x86 / pc586)
* Parrot builds up to miniparrot on same platform
Will Do:
* Work around Parrot bootstraping
20:31 bluescreen joined
chromatic Hello everyone. 20:31
cotto_work hello
mikehh hello 20:32
chromatic Let's review last week and this release. How did it go?
NotFound Hola
mikehh looks good
20:33 ash_ joined
chromatic Did we meet our goals? We didn't merge the GC changes. 20:33
NotFound Surprisingly good, all dynops problem seems to have been worked around.
mikehh make corevm/make coretest now passes
chromatic Any last minute fallout? 20:34
20:34 eternaleye joined
chromatic Sounds like a no. 20:35
What shall we work on this week?
mikehh getting gc_massacre ready to merge? 20:36
chromatic +1 20:37
particle point of interest: rakudo * will not be released this month, and is now targeting post rakudo 2.6, specifically july 29 20:38
the rakudo team plans changes to nqp-rx, which must be included in our next release
20:38 allison joined
particle anything else we do is gravy. 20:38
(from their perspective).
chromatic Are they delaying because of our deprecation policy? 20:39
particle no, they're delaying because they want to release a quality product
Coke you mean post parrot 2.6 ?
chromatic Do they have other requests of Parrot 2.6?
mikehh which of course must also be a quality product :-} 20:40
particle rakudo folks are quite happy with parrot, just need nqp-rx changes (pmichaud++ said about 2 days of his time)
rakudo compiler releases will continue as usual, thursday following parrot
chromatic Okay. Hopefully we can merge and tune gc_massacre.
pmichaud_ particle is correct
particle R* release will be on its own cycle.
pmichaud_ our current plan now is that R* will target the July Parrot release
and we see no major Parrot issues or shortcomings 20:41
(and it's nice that July is a supported Parrot release, which is also a bonus)
Coke I am apparently release both parrot and rakudo next month.
*releasing
(but not R*)
pmichaud_ Coke: excellent
particle coke: been there, done that. it's not hard 20:42
Coke I am going to try to change the release for 2.6 so it highlights things since 2.3 instead of 2.5
chromatic Any Rakudo requests for post 2.5? Don't break trunk for a couple of days?
particle coke++
chromatic: rakudo is currently targeting the 2.5 release 20:43
Coke (and also fix existing warts on 'make html' so we don't have empty pages on docs.parrot.org - if you see doc bugs (not "docs not yet written" but bugs), please mkae sure there's tickets.
we can break trunk all we want. =-)
(WHICH IS NONE!)
particle i think gc_massacre should go in, regardless of when nqp-rx changes are ready (right, pmichaud?)
*should go in when it's ready
chromatic Any other comments on 2.5, 2.6, and Rakudo? 20:44
Coke FYI, 633 active tracs atm.
pmichaud_ if gc_massacre is safe enough for the 2.6 release, then its timing relative to nqp-rx shouldn't be important. 20:45
so it can go in whenever.
mikehh quite a lot were closed in the last week
Coke docs.parrot.org needs to be updated with 2.5
chromatic: for 2.6, we'll need to schedule something in about 2 weeks to review open experimental items.
want to make sure we bless anything that needs it. 20:46
chromatic Good point.
Coke now is also a good time to rip out more deprecated stuff.
chromatic Shall we make that the focus? merge gc_massacre and remove deprecations? 20:47
mikehh as long as there is something that replaces the deprecated stuff or equivalent for needed stuff
Coke That should be the case unless otherwise noted. 20:48
chromatic Let's move to questions. Are there any?
cotto_work q1q 20:49
Coke q1q
chromatic cotto_work? 20:50
cotto_work chromatic and allison (and anyone else who volunteered or wants to), any eta on a first draft of the Lorito docs?
chromatic I'll work on something for next week.
allison Which are the most critical docs to work on first? 20:52
cotto_work They're listed in order of importance on the wiki page
purpose, security, concurrency and balance 20:53
allison I can take concurrency.
cotto_work chromatic, istr that you had purpose 20:54
chromatic yes 20:55
cotto_work ok
plobsing had some thoughts on security and balance. I'll see if I can sucker him into one or both of those.
(should nobody else volunteer) 20:56
eoq
chromatic Coke?
Coke PS next week or no? 20:57
or, "yapc next week may cut down on attendence dramatically."
cotto_work We don't have as many people at yapc as we have in the past. 20:58
chromatic +1 to try
+2 to meet at YAPC
Coke absolutely. there's a parrot/rakudo BOF room available. see you there. 20:59
chromatic Other questions? 21:00
Let's call it a week then. Delete code! 21:01
21:04 NotFound left
tcurtis I've been told that nopastes expire, so here is a link to my report on github: gist.github.com/439694 21:06
Coke tcurtis: just paste it in next time.
danke.
21:07 plobsing_work left 21:09 darbelo left
tcurtis Coke: I tried, but it was not pasting properly(possibly due to line ending problems). Next time I will ensure that my client will not have such problems. 21:11
21:13 whiteknight joined 23:04 eternaleye joined 23:39 mikehh_ 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!