1723d45ad2fd605c8ac12f2d80d363f4a34748fe

Calling panic can cause a compiler to assume any subsequent code is unreachable. Because these panics may or may not be enabled by the build configuration, this can cause developers some pain. Consider: bool bit; if (ptr) bit = ptr->returns_bool(); else panic(); // do stuff with @bit return bit; In this case, @bit is potentially uninitialized when we return! However, the compiler can correctly assume this case is impossible when PANIC_ON_BUG is enabled. Because developers typically enable this feature, the "maybe uninitialized" warning will not be emitted, and the issue remains uncaught until someone tries to make a build without PANIC_ON_BUG. A simple workaround, is to put the definition of QDF_DEBUG_PANIC in another compilation unit, which prevents the compiler from assuming subsequent code is unreachable. For CONFIG_SLUB_DEBUG, do this to catch issues earlier. Otherwise, use the typical inlined approach. Change-Id: I8901fd33781ccb8229fad16343a5b08d97cdcf68 CRs-Fixed: 2202527
This is CNSS WLAN Host Driver for products starting from iHelium
Description
Langue
C
98.7%
C++
0.9%
Makefile
0.3%
Starlark
0.1%