Testing removal of ifdef or configure checks: Difference between revisions
From SambaWiki
(link to helpful gcc -E script) |
|||
| Line 1: | Line 1: | ||
=#ifdef removal is risky= |
=#ifdef removal is risky= |
||
Large-scale removal of "unused" ifdef is an important, but risky task. |
Large-scale removal of "unused" ifdef or the configure checks that produce #defines 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. |
It is difficult (and time consuming) to prove that the code is unused and that there is no change to the compiled output. |
||
Revision as of 01:26, 27 April 2019
#ifdef removal is risky
Large-scale removal of "unused" ifdef or the configure checks that produce #defines 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 is a Python script that wraps gcc -E to attempt to solve this dilemma, so as to provide a result that can be reasoned with via tools like dirdiff