summaryrefslogtreecommitdiff
path: root/lib/mpi/longlong.h
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2020-02-19 22:23:02 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-06-20 10:23:20 +0200
commit2819246ff6a084082d8f2d497f28e47b9c4c62b6 (patch)
treeabbe2d9b79002eac249fda33f42977f4730235bf /lib/mpi/longlong.h
parent5b053e49167b7a58326896e59b42d31e3d9cd3a2 (diff)
e1000: Distribute switch variables for initialization
[ Upstream commit a34c7f5156654ebaf7eaace102938be7ff7036cb ] Variables declared in a switch statement before any case statements cannot be automatically initialized with compiler instrumentation (as they are not part of any execution flow). With GCC's proposed automatic stack variable initialization feature, this triggers a warning (and they don't get initialized). Clang's automatic stack variable initialization (via CONFIG_INIT_STACK_ALL=y) doesn't throw a warning, but it also doesn't initialize such variables[1]. Note that these warnings (or silent skipping) happen before the dead-store elimination optimization phase, so even when the automatic initializations are later elided in favor of direct initializations, the warnings remain. To avoid these problems, move such variables into the "case" where they're used or lift them up into the main function body. drivers/net/ethernet/intel/e1000/e1000_main.c: In function ‘e1000_xmit_frame’: drivers/net/ethernet/intel/e1000/e1000_main.c:3143:18: warning: statement will never be executed [-Wswitch-unreachable] 3143 | unsigned int pull_size; | ^~~~~~~~~ [1] https://bugs.llvm.org/show_bug.cgi?id=44916 Signed-off-by: Kees Cook <keescook@chromium.org> Tested-by: Aaron Brown <aaron.f.brown@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'lib/mpi/longlong.h')
0 files changed, 0 insertions, 0 deletions