suspect-devices/circuitpython/py/mpthread.h, branch encodingCircuitPython - a Python implementation for teaching coding with microcontrollershttps://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=encoding2020-07-06T18:16:25+00:00Add license to some obvious files.2020-07-06T18:16:25+00:00Diego Elio Pettenòflameeyes@flameeyes.com2020-06-03T22:40:05+00:00urn:sha1:34b4993d63a6b576f29d624385c681f679b4124call: Unify header guard usage.2017-07-18T01:57:39+00:00Alexander Steffendevel.20.webmeister@spamgourmet.com2017-06-29T21:14:58+00:00urn:sha1:299bc625864b9e624ed599c94a5f95870516139a
The code conventions suggest using header guards, but do not define how
those should look like and instead point to existing files. However, not
all existing files follow the same scheme, sometimes omitting header guards
altogether, sometimes using non-standard names, making it easy to
accidentally pick a "wrong" example.
This commit ensures that all header files of the MicroPython project (that
were not simply copied from somewhere else) follow the same pattern, that
was already present in the majority of files, especially in the py folder.
The rules are as follows.
Naming convention:
* start with the words MICROPY_INCLUDED
* contain the full path to the file
* replace special characters with _
In addition, there are no empty lines before #ifndef, between #ifndef and
one empty line before #endif. #endif is followed by a comment containing
the name of the guard macro.
py/grammar.h cannot use header guards by design, since it has to be
included multiple times in a single C file. Several other files also do not
need header guards as they are only used internally and guaranteed to be
included only once:
* MICROPY_MPHALPORT_H
* mpconfigboard.h
* mpconfigport.h
* mpthreadport.h
* pin_defs_*.h
* qstrdefs*.h
py/mpthread: Include mpstate.h when defining GIL macros.2016-06-28T10:28:52+00:00Damien Georgedamien.p.george@gmail.com2016-05-31T14:25:40+00:00urn:sha1:77e37ff98bec1ccf6af6edf3efcad26b54da0c47py/modthread: Allow to properly set the stack limit of a thread.2016-06-28T10:28:51+00:00Damien Georgedamien.p.george@gmail.com2016-05-30T15:56:51+00:00urn:sha1:df95f52583e0f5e3f2a74f7461bb00e2f24b3079
We rely on the port setting and adjusting the stack size so there is
enough room to recover from hitting the stack limit.
py/mpthread.h: Move GIL macros outside MICROPY_PY_THREAD block.2016-06-28T10:28:50+00:00Damien Georgedamien.p.george@gmail.com2016-05-27T12:44:55+00:00urn:sha1:e90b6ce0b5af51ef195aa98dad35a185b77c5075
The GIL macros are needed even if threading is not enabled.
py: Implement a simple global interpreter lock.2016-06-28T10:28:50+00:00Damien Georgedamien.p.george@gmail.com2016-05-26T10:42:53+00:00urn:sha1:4cec63a9dbed86c4332b9e7fcd56d092046193e4
This makes the VM/runtime thread safe, at the cost of not being able to
run code in parallel.
py/modthread: Call mp_thread_start/mp_thread_finish around threads.2016-06-28T10:28:49+00:00Damien Georgedamien.p.george@gmail.com2016-05-04T09:52:19+00:00urn:sha1:9172c0cb252faa47f56e61f67ceb213012631de2
So the underlying thread implementation can do any necessary bookkeeping.
py/gc: Make memory manager and garbage collector thread safe.2016-06-28T10:28:49+00:00Damien Georgedamien.p.george@gmail.com2016-04-25T15:28:57+00:00urn:sha1:c93d9caa8b8be81f7e6faf9f2ca2ad16d4942ab8
By using a single, global mutex, all memory-related functions (alloc,
free, realloc, collect, etc) are made thread safe. This means that only
one thread can be in such a function at any one time.
py/modthread: Implement lock object, for creating a mutex.2016-06-28T10:28:49+00:00Damien Georgedamien.p.george@gmail.com2016-04-25T11:21:48+00:00urn:sha1:801d1b3803e4c8070a8bea6ee4f563a799d010b7py/modthread: Add stack_size() function.2016-06-28T10:28:48+00:00Damien Georgedamien.p.george@gmail.com2016-04-25T09:02:47+00:00urn:sha1:707f98f207d85b1de9814e90254d52a78ac19739