CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=0.9.0 2016-09-19T02:28:03+00:00 2016-09-19T02:28:03+00:00 Damien George damien.p.george@gmail.com 2016-09-18T22:46:01+00:00 urn:sha1:adaf0d865cd6c81fb352751566460506392ed55f With the previous patch combining 3 emit functions into 1, it now makes sense to also combine the corresponding VM opcodes, which is what this patch does. This eliminates 2 opcodes which simplifies the VM and reduces code size, in bytes: bare-arm:44, minimal:64, unix(NDEBUG,x86-64):272, stmhal:92, esp8266:200. Profiling (with a simple script that creates many list/dict/set comprehensions) shows no measurable change in performance. 2015-12-10T22:19:48+00:00 Damien George damien.p.george@gmail.com 2015-12-08T12:28:11+00:00 urn:sha1:bdbe8c9ae21559f6dc0b8e1ad84b7bbec2a04726 Fixes #1684 and makes "not" match Python semantics. The code is also simplified (the separate MP_BC_NOT opcode is removed) and the patch saves 68 bytes for bare-arm/ and 52 bytes for minimal/. Previously "not x" was implemented as !mp_unary_op(x, MP_UNARY_OP_BOOL), so any given object only needs to implement MP_UNARY_OP_BOOL (and the VM had a special opcode to do the ! bit). With this patch "not x" is implemented as mp_unary_op(x, MP_UNARY_OP_NOT), but this operation is caught at the start of mp_unary_op and dispatched as !mp_obj_is_true(x). mp_obj_is_true has special logic to test for truthness, and is the correct way to handle the not operation. 2015-06-25T14:42:13+00:00 Damien George damien.p.george@gmail.com 2015-06-25T14:42:13+00:00 urn:sha1:59fba2d6ea31c134c9c0b88dc73cd25b236f167c Previous to this patch each time a bytes object was referenced a new instance (with the same data) was created. With this patch a single bytes object is created in the compiler and is loaded directly at execute time as a true constant (similar to loading bignum and float objects). This saves on allocating RAM and means that bytes objects can now be used when the memory manager is locked (eg in interrupts). The MP_BC_LOAD_CONST_BYTES bytecode was removed as part of this. Generated bytecode is slightly larger due to storing a pointer to the bytes object instead of the qstr identifier. Code size is reduced by about 60 bytes on Thumb2 architectures. 2015-06-13T22:36:30+00:00 Damien George damien.p.george@gmail.com 2015-06-13T21:00:10+00:00 urn:sha1:c5029bcbf37fd1a3fb145d9fa9e4a5094478f17b 2015-05-12T21:46:02+00:00 Damien George damien.p.george@gmail.com 2015-05-11T12:25:19+00:00 urn:sha1:c2a4e4effc81d8ab21bb014e34355643e5ca0da2 Hashing is now done using mp_unary_op function with MP_UNARY_OP_HASH as the operator argument. Hashing for int, str and bytes still go via fast-path in mp_unary_op since they are the most common objects which need to be hashed. This lead to quite a bit of code cleanup, and should be more efficient if anything. It saves 176 bytes code space on Thumb2, and 360 bytes on x86. The only loss is that the error message "unhashable type" is now the more generic "unsupported type for __hash__". 2015-05-05T21:15:42+00:00 Damien George damien.p.george@gmail.com 2015-05-05T21:15:42+00:00 urn:sha1:8872abcbc4107c8d3eaf148a03813e607aa30bfb Ellipsis constant is rarely used so no point having an extra bytecode for it. 2015-02-08T01:57:40+00:00 Damien George damien.p.george@gmail.com 2015-02-08T01:57:40+00:00 urn:sha1:7d414a1b52d193bab2c94cf56932e1eba23ba542 Previous to this patch, a big-int, float or imag constant was interned (made into a qstr) and then parsed at runtime to create an object each time it was needed. This is wasteful in RAM and not efficient. Now, these constants are parsed straight away in the parser and turned into objects. This allows constants with large numbers of digits (so addresses issue #1103) and takes us a step closer to #722. 2015-01-13T15:55:54+00:00 Damien George damien.p.george@gmail.com 2015-01-13T15:55:54+00:00 urn:sha1:dab1385177558f1d27c03b59e443b6fa25a2cdc0 This allows to directly load a Python object to the Python stack. See issue #722 for background. 2015-01-01T20:32:09+00:00 Damien George damien.p.george@gmail.com 2015-01-01T20:27:54+00:00 urn:sha1:51dfcb4bb7613ed164952712d9a5235a7b833cde Addresses issue #1022. 2014-10-25T19:23:13+00:00 Damien George damien.p.george@gmail.com 2014-10-25T15:43:46+00:00 urn:sha1:8456cc017bc2e4a9fe063f485c3f2aa410435015 There is a lot potential in compress bytecodes and make more use of the coding space. This patch introduces "multi" bytecodes which have their argument included in the bytecode (by addition). UNARY_OP and BINARY_OP now no longer take a 1 byte argument for the opcode. Rather, the opcode is included in the first byte itself. LOAD_FAST_[0,1,2] and STORE_FAST_[0,1,2] are removed in favour of their multi versions, which can take an argument between 0 and 15 inclusive. The majority of LOAD_FAST/STORE_FAST codes fit in this range and so this saves a byte for each of these. LOAD_CONST_SMALL_INT_MULTI is used to load small ints between -16 and 47 inclusive. Such ints are quite common and now only need 1 byte to store, and now have much faster decoding. In all this patch saves about 2% RAM for typically bytecode (1.8% on 64-bit test, 2.5% on pyboard test). It also reduces the binary size (because bytecodes are simplified) and doesn't harm performance.