[pypy-dev] Unknown Operation Re: What Causes An Ambiguous low-level helper specialization Error?
andrewfr_ice at yahoo.com
Wed Jan 25 21:05:44 CET 2012
Thanks for the advice! I'll try your suggestion. However I really do wish to work with RPython. Also how do I look at the transaction interface?
A suggestion: to rule out silly mistakes on my end, perhaps someone could try to compile bank.py (the code I posted earlier). That code is based on the example in section 13.4 (Concurrent executions) of the 3rd edition of "Database System Concepts" by Silberschatz et al. I have used this book to write simple post mortem deadlock detection for Stackless python.
I also intend to write a C version of bank.py using the libstm and rstm libraries.
From: Armin Rigo <arigo at tunes.org>
To: Andrew Francis <andrewfr_ice at yahoo.com>
Cc: Amaury Forgeot d'Arc <amauryfa at gmail.com>; "pypy-dev at codespeak.net" <pypy-dev at codespeak.net>
Sent: Wednesday, January 25, 2012 2:06 PM
Subject: Re: Unknown Operation Re: [pypy-dev] What Causes An Ambiguous low-level helper specialization Error?
On Wed, Jan 25, 2012 at 19:56, Andrew Francis <andrewfr_ice at yahoo.com> wrote:
> I can't wait to see this code compile! Bank accounts are the "hello world"
> of transactional programming!
In case you want to avoid having to hack at RPython: by now, you can
also compile the full PyPy with transactions enabled. You just get a
PyPy with no GC at all (so it cannot run for more than a few seconds
before running out of memory). You then get a sane interface from the
built-in module 'transaction', and don't have to write any RPython
I use the following command line (it's very fast and doesn't require
too much RAM, because of no GC):
./translate.py -O1 --gc=none --stm targetpypystandalone.py
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pypy-dev