CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=3.1.1 2018-01-24T18:33:46+00:00 2018-01-24T18:33:46+00:00 Scott Shawcroft scott.shawcroft@gmail.com 2018-01-24T00:22:05+00:00 urn:sha1:416abe33ed44e44d8f75342731080217e123278b This adapts the allocation process to start from either end of the heap when searching for free space. The default behavior is identical to the existing behavior where it starts with the lowest block and looks higher. Now it can also look from the highest block and lower depending on the long_lived parameter to gc_alloc. As the heap fills, the two sections may overlap. When they overlap, a collect may be triggered in order to keep the long lived section compact. However, free space is always eligable for each type of allocation. By starting from either of the end of the heap we have ability to separate short lived objects from long lived ones. This separation reduces heap fragmentation because long lived objects are easy to densely pack. Most objects are short lived initially but may be made long lived when they are referenced by a type or module. This involves copying the memory and then letting the collect phase free the old portion. QSTR pools and chunks are always long lived because they are never freed. The reallocation, collection and free processes are largely unchanged. They simply also maintain an index to the highest free block as well as the lowest. These indices are used to speed up the allocation search until the next collect. In practice, this change may slightly slow down import statements with the benefit that memory is much less fragmented afterwards. For example, a test import into a 20k heap that leaves ~6k free previously had the largest continuous free space of ~400 bytes. After this change, the largest continuous free space is over 3400 bytes. 2017-08-15T01:53:36+00:00 Stefan Naumann me@stefannaumann.de 2017-07-24T16:55:14+00:00 urn:sha1:ace9fb54053c29574bdf81ffacc5ddcf9d4b45d9 It enables all the DEBUG_printf outputs in the py/ source code. 2017-07-31T08:35:40+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-30T07:22:17+00:00 urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e There were several different spellings of MicroPython present in comments, when there should be only one. 2016-11-02T12:15:41+00:00 Colin Hogben colin@infinnovation.co.uk 2016-10-31T14:05:56+00:00 urn:sha1:f9b6b37cf65c4f65c4ad461d439fbf624c0f10c1 In both parse.c and qstr.c, an internal chunking allocator tidies up by calling m_renew to shrink an allocated chunk to the size used, and assumes that the chunk will not move. However, when MICROPY_ENABLE_GC is false, m_renew calls the system realloc, which does not guarantee this behaviour. Environments where realloc may return a different pointer include: (1) mbed-os with MBED_HEAP_STATS_ENABLED (which adds a wrapper around malloc & friends; this is where I was hit by the bug); (2) valgrind on linux (how I diagnosed it). The fix is to call m_renew_maybe with allow_move=false. 2016-09-19T03:18:54+00:00 Damien George damien.p.george@gmail.com 2016-09-19T03:18:54+00:00 urn:sha1:e60835bac5336c8e0123443b427c6db48b5060df qstrs are always null terminated so qstr_str will stay as part of the API. 2016-06-28T10:28:50+00:00 Damien George damien.p.george@gmail.com 2016-05-26T10:53:34+00:00 urn:sha1:a1c93a62b1d1020c5ef3ce1744469a118433d0e5 There is no need since the GIL already makes gc and qstr operations atomic. 2016-06-28T10:28:50+00:00 Damien George damien.p.george@gmail.com 2016-05-26T09:06:46+00:00 urn:sha1:1f54ad2aed0dc8f2d868ccd89ccf639a475e8022 2016-06-15T22:42:48+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-06-15T22:40:31+00:00 urn:sha1:f469c764428230363a2b22fedf303d86eea82853 It has more usages than just qstr extraction, for example, embedding (where people don't care about efficient predefined qstrs). 2016-04-19T08:37:56+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-04-19T08:30:06+00:00 urn:sha1:c618f91e22613b2e530f7c21be0be789a7e8eed5 When there're C files to be (re)compiled, they're all passed first to preprocessor. QSTR references are extracted from preprocessed output and split per original C file. Then all available qstr files (including those generated previously) are catenated together. Only if the resulting content has changed, the output file is written (causing almost global rebuild to pick up potentially renumbered qstr's). Otherwise, it's not updated to not cause spurious rebuilds. Related make rules are split to minimize amount of commands executed in the interim case (when some C files were updated, but no qstrs were changed). 2016-04-13T15:07:47+00:00 Damien George damien.p.george@gmail.com 2016-01-31T22:24:16+00:00 urn:sha1:0a2e9650f5383bc1190d6b27a3d923e313c3d879 The config variable MICROPY_MODULE_FROZEN is now made of two separate parts: MICROPY_MODULE_FROZEN_STR and MICROPY_MODULE_FROZEN_MPY. This allows to have none, either or both of frozen strings and frozen mpy files (aka frozen bytecode).