Details
-
User Story
-
Resolution: Out of scope
-
Not Evaluated
-
None
-
None
-
None
Description
Many programs try to optimize their execution size by remove not used code but this is only happen at the translation unit level and not for the memory layout of members. Very often you use only a little party of the a class, library etc,, People try to strip that down manually with the help of the build system and the preprocessor. But could that not be done automatically by a meta compiler? One that takes C++ in, analyses the usages and outputs C++. All classes, members, functions which are not reached by application could be removed. One idea would be to start from outside, identify the interface and search from there recursive to identify the used resoures. Everything which cannot be reached can be removed. It is quite similar to static analyses. So their are to main areas to research: How to identify the interface to the outside world and the analyses whay is used by this interface.