suspect-devices/circuitpython/py/malloc.c, branch v1.4.1 CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.4.1 2015-03-03T21:23:13+00:00 py: Add MICROPY_MALLOC_USES_ALLOCATED_SIZE to allow simpler malloc API. 2015-03-03T21:23:13+00:00 Damien George damien.p.george@gmail.com 2015-02-27T09:54:12+00:00 urn:sha1:d891452a73165966497f1c79b64276faaa664597 py: Put all global state together in state structures. 2015-01-07T20:33:00+00:00 Damien George damien.p.george@gmail.com 2015-01-01T23:30:53+00:00 urn:sha1:b4b10fd350852e321624d74983cca286091b55a1 This patch consolidates all global variables in py/ core into one place, in a global structure. Root pointers are all located together to make GC tracing easier and more efficient. py: Move to guarded includes, everywhere in py/ core. 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. py: Make gc.enable/disable just control auto-GC; alloc is still allowed. 2014-10-31T21:30:46+00:00 Damien George damien.p.george@gmail.com 2014-10-31T21:30:46+00:00 urn:sha1:109c1de015eeee385020233e2f8cc6f921149103 gc.enable/disable are now the same as CPython: they just control whether automatic garbage collection is enabled or not. If disabled, you can still allocate heap memory, and initiate a manual collection. py: Clean up edge cases of malloc/realloc/free. 2014-10-23T11:02:00+00:00 Damien George damien.p.george@gmail.com 2014-10-23T11:02:00+00:00 urn:sha1:37378f8a9d2b358fdde0f3451d816b7f506846cc py: For malloc and vstr functions, use size_t exclusively for int type. 2014-09-25T14:49:26+00:00 Damien George damien.p.george@gmail.com 2014-09-23T17:10:17+00:00 urn:sha1:b0261341d3706329ea58d8fc1a5ff9c788c9ccf7 It seems most sensible to use size_t for measuring "number of bytes" in malloc and vstr functions (since that's what size_t is for). We don't use mp_uint_t because malloc and vstr are not Micro Python specific. py: Include mpconfig.h before all other includes. 2014-06-21T19:43:22+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2014-06-21T19:43:22+00:00 urn:sha1:59c675a64c1d9757d50ad4627da67a6f996a99fb It defines types used by all other headers. Fixes #691. Add license header to (almost) all files. 2014-05-03T22:27:38+00:00 Damien George damien.p.george@gmail.com 2014-05-03T22:27:38+00:00 urn:sha1:04b9147e150d2d6fa3750f312fe328b6a71c1b28 Blanket wide to all .c and .h files. Some files originating from ST are difficult to deal with (license wise) so it was left out of those. Also merged modpyb.h, modos.h, modstm.h and modtime.h in stmhal/. py, gc: Only zero out the extra bytes at the end of the heap chunk. 2014-04-26T21:23:42+00:00 Damien George damien.p.george@gmail.com 2014-04-26T21:23:42+00:00 urn:sha1:32bef315be8e56ad2d7f69223fe7b9606893b6ab This is a small optimisation to zero out only the additional bytes that the caller did not ask for. py, gc: Zero out newly allocated blocks in the GC. 2014-04-25T22:37:55+00:00 Damien George damien.p.george@gmail.com 2014-04-25T22:37:55+00:00 urn:sha1:daab651c5ca0d7198f6db2fa0abe2399fc08c69e Also add some more debugging output to gc_dump_alloc_table(). Now that newly allocated heap is always zero'd, maybe we just make this a policy for the uPy API to keep it simple (ie any new implementation of memory allocation must zero all allocations). This follows the D language philosophy. Before this patch, a previously used memory block which had pointers in it may still retain those pointers if the new user of that block does not actually use the entire block. Eg, if I want 5 blocks worth of heap, I actually get 8 (round up to nearest 4). Then I never use the last 3, so they keep their old values, which may be pointers pointing to the heap, hence preventing GC. In rare (or maybe not that rare) cases, this leads to long, unintentional "linked lists" within the GC'd heap, filling it up completely. It's pretty rare, because you have to reuse exactly that memory which is part of this "linked list", and reuse it in just the right way. This should fix issue #522, and might have something to do with issue #510.