CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.5.1 2015-11-13T12:49:18+00:00 2015-11-13T12:49:18+00:00 Damien George damien.p.george@gmail.com 2015-11-02T21:55:42+00:00 urn:sha1:d8c834c95d506db979ec871417de90b7951edc30 MICROPY_PERSISTENT_CODE must be enabled, and then enabling MICROPY_PERSISTENT_CODE_LOAD/SAVE (either or both) will allow loading and/or saving of code (at the moment just bytecode) from/to a .mpy file. 2015-11-13T12:49:18+00:00 Damien George damien.p.george@gmail.com 2015-11-02T17:27:18+00:00 urn:sha1:c8e9c0d89afa90694790fd48e1bf527487a5beb7 Main changes when MICROPY_PERSISTENT_CODE is enabled are: - qstrs are encoded as 2-byte fixed width in the bytecode - all pointers are removed from bytecode and put in const_table (this includes const objects and raw code pointers) Ultimately this option will enable persistence for not just bytecode but also native code. 2015-11-13T12:49:18+00:00 Damien George damien.p.george@gmail.com 2015-10-23T00:23:11+00:00 urn:sha1:713ea1800d1f0c82a0c75885ad034705556ab5ef Contains just argument names at the moment but makes it easy to add arbitrary constants. 2015-11-13T12:49:18+00:00 Damien George damien.p.george@gmail.com 2015-10-22T22:45:37+00:00 urn:sha1:3a3db4dcf0400cffef860f61a84979cb1f7a7541 2015-11-13T12:49:18+00:00 Damien George damien.p.george@gmail.com 2015-03-18T17:47:47+00:00 urn:sha1:9b7f583b0ca37ee87e5fb82e2d65fcd96a609b2f 2015-09-23T10:47:01+00:00 Damien George damien.p.george@gmail.com 2015-09-23T10:47:01+00:00 urn:sha1:fbcaf0ea18d647adc445dc1029392c2a908cf540 Saves a few bytes of code space and eliminates need for rot_two bytecode (hence saving RAM and execution time, by a tiny bit). 2015-09-04T15:53:46+00:00 Damien George damien.p.george@gmail.com 2015-09-04T15:53:46+00:00 urn:sha1:3a2171e4061f3a6e3f00c28edf78ff9473355887 2015-08-17T11:51:26+00:00 Damien George damien.p.george@gmail.com 2015-08-14T11:24:11+00:00 urn:sha1:65dc960e3b22a8426e369607e47c19b380ce30ea unix-cpy was originally written to get semantic equivalent with CPython without writing functional tests. When writing the initial implementation of uPy it was a long way between lexer and functional tests, so the half-way test was to make sure that the bytecode was correct. The idea was that if the uPy bytecode matched CPython 1-1 then uPy would be proper Python if the bytecodes acted correctly. And having matching bytecode meant that it was less likely to miss some deep subtlety in the Python semantics that would require an architectural change later on. But that is all history and it no longer makes sense to retain the ability to output CPython bytecode, because: 1. It outputs CPython 3.3 compatible bytecode. CPython's bytecode changes from version to version, and seems to have changed quite a bit in 3.5. There's no point in changing the bytecode output to match CPython anymore. 2. uPy and CPy do different optimisations to the bytecode which makes it harder to match. 3. The bytecode tests are not run. They were never part of Travis and are not run locally anymore. 4. The EMIT_CPYTHON option needs a lot of extra source code which adds heaps of noise, especially in compile.c. 5. Now that there is an extensive test suite (which tests functionality) there is no need to match the bytecode. Some very subtle behaviour is tested with the test suite and passing these tests is a much better way to stay Python-language compliant, rather than trying to match CPy bytecode. 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-05-06T12:55:33+00:00 Damien George damien.p.george@gmail.com 2015-05-06T12:55:33+00:00 urn:sha1:9a42eb541eb426a04bb0541ccf0e26ce82bdcb22 Addresses issue #1226.