suspect-devices/circuitpython/py/qstr.c, branch 2.xCircuitPython - a Python implementation for teaching coding with microcontrollershttps://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=2.x2017-08-15T01:53:36+00:00py: Add verbose debug compile-time flag MICROPY_DEBUG_VERBOSE.2017-08-15T01:53:36+00:00Stefan Naumannme@stefannaumann.de2017-07-24T16:55:14+00:00urn:sha1:ace9fb54053c29574bdf81ffacc5ddcf9d4b45d9
It enables all the DEBUG_printf outputs in the py/ source code.
all: Use the name MicroPython consistently in comments2017-07-31T08:35:40+00:00Alexander Steffendevel.20.webmeister@spamgourmet.com2017-06-30T07:22:17+00:00urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e
There were several different spellings of MicroPython present in comments,
when there should be only one.
py: Fix wrong assumption that m_renew will not move if shrinking2016-11-02T12:15:41+00:00Colin Hogbencolin@infinnovation.co.uk2016-10-31T14:05:56+00:00urn: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.
py/qstr: Remove a comment.2016-09-19T03:18:54+00:00Damien Georgedamien.p.george@gmail.com2016-09-19T03:18:54+00:00urn:sha1:e60835bac5336c8e0123443b427c6db48b5060df
qstrs are always null terminated so qstr_str will stay as part of the API.
py: Don't use gc or qstr mutex when the GIL is enabled.2016-06-28T10:28:50+00:00Damien Georgedamien.p.george@gmail.com2016-05-26T10:53:34+00:00urn:sha1:a1c93a62b1d1020c5ef3ce1744469a118433d0e5
There is no need since the GIL already makes gc and qstr operations
atomic.
py: Make interning of qstrs thread safe.2016-06-28T10:28:50+00:00Damien Georgedamien.p.george@gmail.com2016-05-26T09:06:46+00:00urn:sha1:1f54ad2aed0dc8f2d868ccd89ccf639a475e8022py: Rename __QSTR_EXTRACT flag to NO_QSTR.2016-06-15T22:42:48+00:00Paul Sokolovskypfalcon@users.sourceforge.net2016-06-15T22:40:31+00:00urn:sha1:f469c764428230363a2b22fedf303d86eea82853
It has more usages than just qstr extraction, for example, embedding (where
people don't care about efficient predefined qstrs).
py: Rework QSTR extraction to work in simple and obvious way.2016-04-19T08:37:56+00:00Paul Sokolovskypfalcon@users.sourceforge.net2016-04-19T08:30:06+00:00urn: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).
py: Add ability to have frozen persistent bytecode from .mpy files.2016-04-13T15:07:47+00:00Damien Georgedamien.p.george@gmail.com2016-01-31T22:24:16+00:00urn: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).
py/qstr: Use size_t instead of mp_uint_t when counting allocated bytes.2015-12-17T12:41:40+00:00Damien Georgedamien.p.george@gmail.com2015-12-17T12:41:40+00:00urn:sha1:257848587fb03879e145a34c8065927cf4d1532f