Menu

Advanced Policy Functional

I am currently trying to finish "Advanced" policy but the endeavor occurred really time-consuming. As for [c153580] it is functional, comes with following limitations:

  • Only the content of ./Evolving and ./Stable is partitioned.
  • Vague evolving symbols are not partitioned yet.
  • no decent info on sizes of RAM and ROM sections yet.
  • no explicit hints during build of why SplitCode performance degrades and uC requires reflashing.

The core of the idea is functional and there are no limitations on which resource references which - SplitCode manages that part as expected!
This was the hardest part of all.

The downside of current implementation of "Advanced" policy is that I had to add an extensive printf debugging code to makefile algorithm. Every partitioning step is now verbose and additionally documented in .def and .ref files created for every object file. This printfing debugging and accessing files hundreds of times slows down the building process horribly. Perhaps some makefile-fu could improve that later (todo).
The greatest advantage of all is that these debugging files allow to diff two consecutive builds and give an explicit (and automated) hint on what has actually changed!

Now my plan is to make that diff usable.

Posted by Brutte 2014-01-31 Labels: Advanced

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.