Hana =?utf-8?q?Dusíková?= <hani...@hanicka.net>, Hana =?utf-8?q?Dusíková?= <hani...@hanicka.net>, Hana =?utf-8?q?Dusíková?= <hani...@hanicka.net>, Hana =?utf-8?q?Dusíková?= <hani...@hanicka.net>, Hana =?utf-8?q?Dusíková?= <hani...@hanicka.net>, Hana =?utf-8?q?Dusíková?= <hani...@hanicka.net>, Hana =?utf-8?q?Dusíková?= <hani...@hanicka.net> Message-ID: In-Reply-To: <llvm.org/llvm/llvm-project/pull/98...@github.com>
================ @@ -4340,6 +4340,18 @@ whole system, the current device, an OpenCL workgroup, wavefront, or just a single thread. If these are used on a target that does not support atomic scopes, then they will behave exactly as the standard GNU atomic builtins. +Constant evaluatable atomic builtins +------------------------------------ + +Clang supports constant evaluation of all ``__c11_atomic_*`` and GCC-compatible +``__atomic_*`` builtins. Behaviour of identical as if evaluating these builtins +in a single-threaded environment. + +(Note the GCC-compatible ``__atomic_fetch_OP`` and ``__atomic_OP_fetch`` +builtins with a pointer argument operates as if pointer was pointing to bytes. +Evaluating these builtins which would result in a non-aligned pointer to pointee ---------------- AaronBallman wrote: ```suggestion builtins with a pointer argument operates as if the pointer was pointing to bytes. Evaluating these builtins in a way which would result in a non-aligned pointer to pointee ``` https://github.com/llvm/llvm-project/pull/98756 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
