diff options
| author | Marc Mutz <[email protected]> | 2025-06-06 16:40:48 +0200 |
|---|---|---|
| committer | Marc Mutz <[email protected]> | 2025-06-09 20:36:40 +0000 |
| commit | 8f4ffb72f9e49702f878222b785cf0efc871ee9c (patch) | |
| tree | aa86900d2b8c388df15dcecc9ac2d7539ee6e316 /examples/widgets/graphicsview/chip | |
| parent | 49db71bb1995d8fa71afedb9b461d5203fbe49b1 (diff) | |
Until C++17 (inclusive), a default-constructed std::atomic object can,
officially, only be initialized with a call to std::atomic_init, for
which QBasicAtomic doesn't have API. It is even unclear whether
zero-initialization of static and thread-local objects will cause the
object to be initialized.
To fix, port from QBasicAtomic to QAtomic (which initializes to zero).
Task-number: QTBUG-137465
Pick-to: 6.10 6.9 6.8 6.5
Change-Id: I31a95b36506c376ef0817ef3d61bd8ca02371585
Reviewed-by: Thiago Macieira <[email protected]>
Diffstat (limited to 'examples/widgets/graphicsview/chip')
0 files changed, 0 insertions, 0 deletions