[pypy-dev] Helping with STM at the PyCon 2013 (Santa Clara) sprints
Taavi Burns
taavi.burns at gmail.com
Thu Feb 14 00:20:47 CET 2013
That sounds like a reasonable place to start, thanks!
I tried running the translation, and immediately hit what looks like a
failure from merging in default, due to the pypy/rpython move. I've
got a patch currently pushing to bitbucket, but it'll be a few minutes
(pushing ~10 months of pypy dev effort). It'll be at
https://bitbucket.org/taavi_burns/pypy/commits/0378c78cc316 when the
push finishes. :)
The translation still eventually fails, though:
[translation:ERROR] File
"../../rpython/translator/stm/jitdriver.py", line 86, in
check_jitdriver
[translation:ERROR] assert not jitdriver.autoreds # XXX
[translation:ERROR] AssertionError
Full stack and software versions:
https://gist.github.com/taavi/4949322
Any ideas? Thanks!
On Wed, Feb 13, 2013 at 11:16 AM, Armin Rigo <arigo at tunes.org> wrote:
> Hi Taavi,
>
> On Wed, Feb 13, 2013 at 4:56 PM, Taavi Burns <taavi.burns at gmail.com> wrote:
>> From the list above, are there any particular areas (tickets?) that
>> would be a good starting place for me to look at?
>
> I can't just give you a specific task to do, but you can try to
> understand what is here so far. Look at the branch "stm-thread-2" on
> the pypy repository; e.g. try to translate with "rpython -O2 --stm
> targetpypystandalone". This gives you a kind-of-GIL-less PyPy. Try
> to use the transaction module ("import transaction") on some demo
> programs. Then I suppose you should dive into the mess that is
> multithreaded programming by looking in depth at
> lib_pypy/transaction.py. And this is all before diving into the PyPy
> sources themselves...
>
> You may also look at the work done by Remi Meier on his own separate
> repository (https://bitbucket.org/Raemi/pypy-stm-logging). It
> contains mostly playing around with various ideas that haven't been
> integrated back, or not yet.
>
>
> A bientôt,
>
> Armin.
--
taa
/*eof*/
More information about the pypy-dev
mailing list