Messages in this thread |  | | From | Keith Owens <> | Subject | Re: [PATCH] Re: 2.4.6p6: dep_{bool,tristate} $CONFIG_ARCH_xxx bugs | Date | Mon, 02 Jul 2001 16:21:25 +1000 |
| |
On Sun, 1 Jul 2001 22:52:04 -0700, "Adam J. Richter" <adam@yggdrasil.com> wrote: > In linux-2.4.6-pre8, there are only three configuration variables >that are defined with an indented 'define_bool' statement >(CONFIG_BLK_DEV_IDE{DMA,PCI}, and CONFIG_PCI), and the conditional >code execute by all "if" statements in all of the config.in files >appears to be indented (or at least the first statement in the block >is indented). None of these three variables has the semantics that >I think you you described above.
A conditioned define_bool is not the only possibility, that was just one example. Undefined variables can be created by any of the ask, define, dependent or choice statements listed in Documentation/kbuild/config-language.txt, when that statement is not executed. The reason for not being executed can be an 'if' statement or the code can be in a file that is not read, either the 'source' statement is bypassed or it is for another architecture. Also the unset statement changes variables to undefined values.
Identifying where variables can have unset values cannot be done by a grep of the files. You have to follow every branch of the condition tree, including source statements, eliminate those variables where every branch assigns a value before it is used then flag the remainder as "may be used while uninitialized".
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |