Testing removal of ifdef or configure checks: Difference between revisions
From SambaWiki
(New page for my gcc-E script) |
|||
| Line 7: | Line 7: | ||
==A script to help== |
==A script to help== |
||
This script wraps gcc -E to attempt to solve this dilemma, so as to provide a result that can be reasoned with via tools like [https://www.samba.org/ftp/paulus/ dirdiff] |
[[This script wraps gcc -E|File:Gcc-E.py.txt]] to attempt to solve this dilemma, so as to provide a result that can be reasoned with via tools like [https://www.samba.org/ftp/paulus/ dirdiff] |
||
Revision as of 01:22, 27 April 2019
#ifdef removal is risky
Large-scale removal of "unused" ifdef is an important, but risky task.
It is difficult (and time consuming) to prove that the code is unused and that there is no change to the compiled output.
A script to help
File:Gcc-E.py.txt to attempt to solve this dilemma, so as to provide a result that can be reasoned with via tools like dirdiff