diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-12-11 12:01:10 +0100 |
|---|---|---|
| committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2018-12-28 12:44:38 +0100 |
| commit | 979f2b2f7936f4b71a3100baf2d16c8057f027eb (patch) | |
| tree | 02cc885fdf217e12d7cea210136a04fedf206667 /scripts/kconfig/zconf.y | |
| parent | kconfig: update current_pos in the second lexer (diff) | |
| download | linux-979f2b2f7936f4b71a3100baf2d16c8057f027eb.tar.xz linux-979f2b2f7936f4b71a3100baf2d16c8057f027eb.zip | |
kconfig: remove keyword lookup table entirely
Commit 7a88488bbc23 ("[PATCH] kconfig: use gperf for kconfig keywords")
introduced gperf for the keyword lookup.
Then, commit bb3290d91695 ("Remove gperf usage from toolchain") killed
the gperf use. As a result, the linear keyword search was left behind.
If we do not use gperf, there is no reason to have the separate table
of the keywords. Move all keywords back to the lexer.
I also refactored the lexer to remove the COMMAND and PARAM states.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to '')
| -rw-r--r-- | scripts/kconfig/zconf.y | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/scripts/kconfig/zconf.y b/scripts/kconfig/zconf.y index 3a3ada6f0729..6fb80f210dfb 100644 --- a/scripts/kconfig/zconf.y +++ b/scripts/kconfig/zconf.y @@ -110,11 +110,6 @@ static struct menu *current_menu, *current_entry; menu_end_menu(); } if_entry menu_entry choice_entry -%{ -/* Include kconf_id.c here so it can see the token constants. */ -#include "kconf_id.c" -%} - %% input: mainmenu_stmt stmt_list | stmt_list; |