Jim Mussared

I have re-worked this from scratch. * "hot" functions can be annotated with a per-function `MICROPY_WRAP_FOO` (as before, except now `gc_alloc`, `gc_free`, and `gc_realloc` are included, as well as the...

However, the results are still counter-intuitive (as suggested in the first comment in this PR). As before, adding `-O3` (or `-O2`) seems to be actually harmful. The best results I...

The next step here would be to apply a similar idea to functions that need to be attributed for correctness (i.e. code that must be in RAM). ESP8266 does this...

Another open question is, if you apply the optimise attribute to a function, does that "propagate" to e.g. a called function (in particular, if that function is static inline).

Thanks @xuancong84 - This is definitely a much more straightforward solution than e.g. yaota8266. However a number of issues need to be addressed: 1. The branch needs to be cleanly...

> I have force committed many times so as to get pass as many checks as possible, but I am really not sure how to rebase cleanly as so to...

(And `git push -f` at the end once you've re-made your commit. Despite what git and many guides tell you, force push is a totally normal and expected thing to...

> Error: Process completed with exit code 1. > What does it mean? The rest of the output above that line is the diff reported by the code formatting tool....

> The configuration is at micropython/tools/uncrustify,cfg. The command line I use is: You can't run uncrustify directly, as there are additional rules applied (that cannot be expressed in uncrustify config)....

Great idea! Worth noting that this isn't just important for hard IRQs but also GIL-free multi-core (on e.g. rp2) where the problem is much more likely to occur.