diff options
author | Masahiro Yamada <masahiroy@kernel.org> | 2024-06-04 01:19:04 +0900 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2024-06-06 20:09:10 +0900 |
commit | 77a92660d8fe8d29503fae768d9f5eb529c88b36 (patch) | |
tree | c52b053593190fe11f55a4a038769f5188ea3e49 /scripts/generate_rust_analyzer.py | |
parent | 45c7f555bf5e716d9c6ffb737e97d4cc9b4c21ef (diff) | |
download | lwn-77a92660d8fe8d29503fae768d9f5eb529c88b36.tar.gz lwn-77a92660d8fe8d29503fae768d9f5eb529c88b36.zip |
kconfig: remove wrong expr_trans_bool()
expr_trans_bool() performs an incorrect transformation.
[Test Code]
config MODULES
def_bool y
modules
config A
def_bool y
select C if B != n
config B
def_tristate m
config C
tristate
[Result]
CONFIG_MODULES=y
CONFIG_A=y
CONFIG_B=m
CONFIG_C=m
This output is incorrect because CONFIG_C=y is expected.
Documentation/kbuild/kconfig-language.rst clearly explains the function
of the '!=' operator:
If the values of both symbols are equal, it returns 'n',
otherwise 'y'.
Therefore, the statement:
select C if B != n
should be equivalent to:
select C if y
Or, more simply:
select C
Hence, the symbol C should be selected by the value of A, which is 'y'.
However, expr_trans_bool() wrongly transforms it to:
select C if B
Therefore, the symbol C is selected by (A && B), which is 'm'.
The comment block of expr_trans_bool() correctly explains its intention:
* bool FOO!=n => FOO
^^^^
If FOO is bool, FOO!=n can be simplified into FOO. This is correct.
However, the actual code performs this transformation when FOO is
tristate:
if (e->left.sym->type == S_TRISTATE) {
^^^^^^^^^^
While it can be fixed to S_BOOLEAN, there is no point in doing so
because expr_tranform() already transforms FOO!=n to FOO when FOO is
bool. (see the "case E_UNEQUAL" part)
expr_trans_bool() is wrong and unnecessary.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions