MicroPython Forum (Archive)

Would this do the job for you ?


Jan

Hello all micropython fans, I have recently given a talk at PyCon CZ 2017 about a small fun project that runs micropython as one of freertos tasks. Except for the use case, that itself is interesting but not new, I would like to know everyone's opinions on the build/configuration solution. The talk ...

A proof-of-concept is now available:

https://github.com/micropython/micropython/pull/1899

Looking forward to any comments within the PR

Jan

The automated qstring extraction actually reveals interesting things -> some strings are not being used but the qstrdefsport.h doesn't contain proper ifdefs around it, while the relevant part of the code that uses the qstring has the ifdef. Anyway, the topic is not as trivial and I know understand a...

I have fixed the script to handle nested ifdefs properly: https://gist.github.com/honzik666/23def819ee6285eebc97 Let me know if anything is still not in line...

The build system changes are minimal, I will make some tests tomorrow and post it to github tomorrow. I am curious if Dave likes it

Jan

I am drafting a prototype - patch into the build system

The b) approach is straightfully usable including the ifdef hell. I like it as it could be possible to integrate it into the build process. I have looked into the build system a bit and it seems that it is not as easy since each .o compilation step has dependency generation as a side effect. A trivi...

qstr generation is something that should definitely be looked into. I believe the point is to not bloat sources with #ifdefs or even better to ban the use of ifdefs except for header file guards ;-) Stick is in much better position while generating qstr definitions since with python reflection the g...

Let's see what happens in the long run. The notes are available here: https://github.com/braiins/micropython/ ... ting-Notes for the time being.

Any comments on misinterpretation/improvements are welcome.

Best regards,

Jan

The way the gc works is that anything that is "referenced" (i.e. has a pointer to it) is considered to be in use. So the gc looks through the stack (since registers and local variables on the stack can contain pointers to nwely allocated objects) and as a performance optimization, rather than looki...