JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.
If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.
If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.
| CodeSonar® 9.0p0 Hot Tips | CONFIDENTIAL | CodeSecure Inc |
A function call specifies an atomic memory order that is not memory_order_seq_cst.
Checks for this warning class apply to the stdatomic.h functions that have explicit atomic memory order (memory_order) parameters.
| Class Name | Risky Atomic Memory Order | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Significance | reliability | |||||||||
| Mnemonic | CONCURRENCY.C_ATOMIC.MO | |||||||||
| Categories |
|
|||||||||
| Availability | Available for C and C++. |
|||||||||
| Enabling | Checks for this warning class are
disabled by default. To enable them, add the following WARNING_FILTER
rule to the project configuration file.
WARNING_FILTER += allow class="Risky Atomic Memory Order" |
Japanese (ja)
#include <stdatomic.h>
_Atomic int avar;
void c_atomic_mo( void ) {
int nvar = 1;
atomic_init(&avar, nvar+1);
nvar += atomic_load(&avar); /* ok: atomic_load() uses memory_order_seq_cst implicitly */
nvar += atomic_load_explicit(&avar, memory_order_seq_cst); /* ok: call specifies memory_order_seq_cst explicitly */
/* 'Risky Atomic Memory Order' warning issued on following line
* - call specifies memory_order_relaxed
*/
nvar += atomic_load_explicit(&avar, memory_order_relaxed);
/* 'Risky Atomic Memory Order' warning issued on following line
* - call specifies memory_order_relaxed
*/
atomic_store_explicit(&avar, nvar, memory_order_relaxed);
}
The following configuration file parameters affect checks for this warning class.