… | |
… | |
2 | |
2 | |
3 | TODO: should explore PerlIO::coroaio (perl leaks like hell). |
3 | TODO: should explore PerlIO::coroaio (perl leaks like hell). |
4 | TODO: channel->maxsize(newsize)? |
4 | TODO: channel->maxsize(newsize)? |
5 | TODO: http://www.microsoft.com/msj/archive/s2ce.aspx |
5 | TODO: http://www.microsoft.com/msj/archive/s2ce.aspx |
6 | |
6 | |
7 | TODO: tutorial |
7 | - "improve portability to Gentoo" - gentoo manages to put perl variables |
8 | TODO: in_eval, PL_tained |
8 | in memory areas that are farther than 2gb apart, which the jit couldn't |
|
|
9 | handle and barfed. now it's just a bit slower on gentoo. |
|
|
10 | |
|
|
11 | 6.01 Sun Jul 3 12:31:14 CEST 2011 |
|
|
12 | - workarounds are good, but the test for whether pthreads are used |
|
|
13 | was not good. thisone should be better. |
|
|
14 | - check differently whether gcc generates cfi instructions itself. |
|
|
15 | |
|
|
16 | 6.0 Wed Jun 29 19:43:35 CEST 2011 |
9 | - INCOMPATIBLE CHANGE: unreferenced coro objects will now be |
17 | - INCOMPATIBLE CHANGE: unreferenced coro objects will now be |
10 | destroyed and cleaned up automatically (e.g. async { schedule }). |
18 | destroyed and cleaned up automatically (e.g. async { schedule }). |
11 | - implement a JIT compiler for part of the thread switch code, |
19 | - implement a JIT compiler for part of the thread switch code, |
12 | which gives a 50% speed improvement on threaded perls, and |
20 | which gives a 50% speed improvement on threaded perls, and |
13 | about 4% on non-thraeded perls (so threaded perls now finally |
21 | about 4% on non-thraeded perls (so threaded perls now finally |
14 | reach about half the speed of non-threaded perls). |
22 | reach about half the speed of non-threaded perls). |
|
|
23 | - slightly modernise Coro::Intro, add section about rouse functions. |
15 | - avoid DEFSV and ERRSV, giving another 10% improvement |
24 | - avoid DEFSV and ERRSV, giving another 10% improvement |
16 | in thread switching. |
25 | in thread switching. |
17 | - Coro::State->is_destroyed is now called is_zombie. |
26 | - Coro::State->is_destroyed is now called is_zombie. |
18 | - implement a Coro->safe_cancel method that might fail, but |
27 | - implement a Coro->safe_cancel method that might fail, but |
19 | cancels in a "safer" way if it succeeds. |
28 | cancels in a "safer" way if it succeeds. |
|
|
29 | - add preliminary support for DEBUGGING perls. |
20 | - get rid of two hash-accesses when initialising a new Coro - this |
30 | - get rid of two hash-accesses when initialising a new Coro - this |
21 | speeds up coro creation by almost a factor of two. |
31 | speeds up coro creation by almost a factor of two. |
22 | - croak when a coro that is being cancelled tries to block |
32 | - croak when a coro that is being cancelled tries to block |
23 | (e.g. while executing a guard block), instead of crashing or |
33 | (e.g. while executing a guard block), instead of crashing or |
24 | deadlocking. |
34 | deadlocking. |
… | |
… | |
40 | threads by nulling the pointers on clone. |
50 | threads by nulling the pointers on clone. |
41 | - simplify warn/die hook handling when loading Coro - the convoluted |
51 | - simplify warn/die hook handling when loading Coro - the convoluted |
42 | logic seems to be no longer neccessary. |
52 | logic seems to be no longer neccessary. |
43 | - use libecb instead of our own home-grown gcc hacks. |
53 | - use libecb instead of our own home-grown gcc hacks. |
44 | - document alternatives to Coro::LWP. Please use them :) |
54 | - document alternatives to Coro::LWP. Please use them :) |
|
|
55 | - work around another mindless idiotic NEEDLESS bug in openbsd/mirbsds |
|
|
56 | sigaltstack. Really. wine suffers from it, erlang suffers from it, |
|
|
57 | and it's known since at least 2006. |
45 | |
58 | |
46 | 5.372 Wed Feb 23 06:14:30 CET 2011 |
59 | 5.372 Wed Feb 23 06:14:30 CET 2011 |
47 | - apparently mingw doesn't provide a working gettimeofday, try to |
60 | - apparently mingw doesn't provide a working gettimeofday, try to |
48 | work around that by relying on Time::HiRes (indirectly brought to |
61 | work around that by relying on Time::HiRes (indirectly brought to |
49 | my attention by Max Maischein). |
62 | my attention by Max Maischein). |