CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.9.2 2017-07-31T08:35:40+00:00 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. 2017-06-29T07:40:25+00:00 Damien George damien.p.george@gmail.com 2017-06-29T07:40:25+00:00 urn:sha1:265500c5c80a8b32a10676487c04f374ec359ab2 Prior to this patch there were 2 paths for creating the namedtuple, one for when no keyword args were passed, and one when there were keyword args. And alloca was used in the keyword-arg path to temporarily create the array of elements for the namedtuple, which would then be copied to a heap-allocated object (the namedtuple itself). This patch simplifies the code by combining the no-keyword and keyword paths, and removing the need for the alloca by constructing the namedtuple on the heap before populating it. Heap usage in unchanged, stack usage is reduced, use of alloca is removed, and code size is not increased and is actually reduced by between 20-30 bytes for most ports. 2017-04-12T03:22:21+00:00 Damien George damien.p.george@gmail.com 2017-04-06T02:09:01+00:00 urn:sha1:816413e4b20ccd463321558458bb63c310712bca The common cases for inheritance are 0 or 1 parent types, for both built-in types (eg built-in exceptions) as well as user defined types. So it makes sense to optimise the case of 1 parent type by storing just the type and not a tuple of 1 value (that value being the single parent type). This patch makes such an optimisation. Even though there is a bit more code to handle the two cases (either a single type or a tuple with 2 or more values) it helps reduce overall code size because it eliminates the need to create a static tuple to hold single parents (eg for the built-in exceptions). It also helps reduce RAM usage for user defined types that only derive from a single parent. Changes in code size (in bytes) due to this patch: bare-arm: -16 minimal (x86): -176 unix (x86-64): -320 unix nanbox: -384 stmhal: -64 cc3200: -32 esp8266: -108 2017-03-29T01:56:17+00:00 Damien George damien.p.george@gmail.com 2017-03-25T08:35:08+00:00 urn:sha1:6213ad7f466df12c734dc527993bbb46c9d9eb5c This patch changes mp_uint_t to size_t for the len argument of the following public facing C functions: mp_obj_tuple_get mp_obj_list_get mp_obj_get_array These functions take a pointer to the len argument (to be filled in by the function) and callers of these functions should update their code so the type of len is changed to size_t. For ports that don't use nan-boxing there should be no change in generate code because the size of the type remains the same (word sized), and in a lot of cases there won't even be a compiler warning if the type remains as mp_uint_t. The reason for this change is to standardise on the use of size_t for variables that count memory (or memory related) sizes/lengths. It helps builds that use nan-boxing. 2017-03-24T06:25:25+00:00 Damien George damien.p.george@gmail.com 2017-03-24T06:25:25+00:00 urn:sha1:f4ee1ba9b48870bb0e3d07dcd6fa3913b500b9ec 2016-10-17T01:17:37+00:00 Damien George damien.p.george@gmail.com 2016-10-17T01:17:37+00:00 urn:sha1:7d0d7215d2575a2d36d34c9a13b58cade0610a28 Saves the following number of bytes of code space: 176 for bare-arm, 352 for minimal, 272 for unix x86-64, 140 for stmhal, 120 for esp8266. 2016-05-23T20:08:07+00:00 Antonin ENFRUN antonin.e@me.com 2016-05-22T17:28:04+00:00 urn:sha1:ca41dc27504c68e805472a6788c4cddbb0da28b1 So the documentation's example works. Besides, a tuple can be more memory efficient. 2016-03-14T22:40:39+00:00 Damien George damien.p.george@gmail.com 2016-03-14T22:40:39+00:00 urn:sha1:2a1cca20b1e1a93c86c8c3a3254ab7150c85ac08 Passing an mp_uint_t to a %d printf format is incorrect for builds where mp_uint_t is larger than word size (eg a nanboxing build). This patch adds some simple casting to int in these cases. 2016-01-11T00:49:27+00:00 Damien George damien.p.george@gmail.com 2016-01-03T15:55:55+00:00 urn:sha1:5b3f0b7f39bd67cc9182993c288f09f67a0890df The first argument to the type.make_new method is naturally a uPy type, and all uses of this argument cast it directly to a pointer to a type structure. So it makes sense to just have it a pointer to a type from the very beginning (and a const pointer at that). This patch makes such a change, and removes all unnecessary casting to/from mp_obj_t. 2016-01-11T00:48:41+00:00 Damien George damien.p.george@gmail.com 2016-01-03T09:59:18+00:00 urn:sha1:a0c97814dfcb0debbde8be99539e3d5ca2334e54 This patch changes the type signature of .make_new and .call object method slots to use size_t for n_args and n_kw (was mp_uint_t. Makes code more efficient when mp_uint_t is larger than a machine word. Doesn't affect ports when size_t and mp_uint_t have the same size.