28fc46ee09
We were testing the value of a volatile variable inside a zassert, which static analysis doesn't like. In principle, it might be volatile because it's an MMIO register or something and the read is a side effect, and an assertion will be optionally compiled. (Except here the value is just regular memory marked volatile for threadsafety, and zassert will never be elided in a test, but the tool doesn't know that). Refactor a little so we always read the variable in a way the tool can detect is consistent. Fixes #18446 Signed-off-by: Andy Ross <andrew.j.ross@intel.com> |
||
|---|---|---|
| .. | ||
| main.c | ||
| test_priority_scheduling.c | ||
| test_sched_is_preempt_thread.c | ||
| test_sched_priority.c | ||
| test_sched_timeslice_and_lock.c | ||
| test_sched_timeslice_reset.c | ||
| test_sched.h | ||
| test_slice_scheduling.c | ||
| user_api.c | ||