diff options
| author | Paul Eggert | 2025-01-26 23:04:21 -0800 |
|---|---|---|
| committer | Paul Eggert | 2025-01-26 23:05:55 -0800 |
| commit | 1ed769a3cb753a86badba8a2878fa788a6fdc1f8 (patch) | |
| tree | 3479d096e71014fa8b182480affee76f27f0261f /java/Makefile.in | |
| parent | a5c47258ffe6d037e3e3c3665ca82a18661cc82c (diff) | |
| download | emacs-1ed769a3cb753a86badba8a2878fa788a6fdc1f8.tar.gz emacs-1ed769a3cb753a86badba8a2878fa788a6fdc1f8.zip | |
Pacify -Wanalyzer-use-of-uninitialized-value
With ‘configure --enable-gcc-warnings’,
gcc (GCC) 14.2.1 20250110 (Red Hat 14.2.1-7) on x86-64
complained, as it apparently did not want to assume that enum
variables have one of the listed values.
Work around the problem by using tables rather than
switch statements. This gives up a little static
checking but I don’t see any other easy way to pacify
GCC without disabling the warnings entirely.
* src/pdumper.c (dump_fwd_int, dump_fwd_bool, dump_fwd_obj)
(dump_fwd_buffer_obj, dump_fwd_kboard_obj):
Last arg is now void const * so that these functions’ addresses
can all be put into the same array.
(dump_fwd, dump_anonymous_allocate_posix, dump_map_file_posix):
Use an array rather than a switch.
(mem_prot_posix_table): New static constant table.
Diffstat (limited to 'java/Makefile.in')
0 files changed, 0 insertions, 0 deletions