[Bug c/95378] __atomic_load will write to objects of cv-qualified types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95378 Jonathan Wakely changed: What|Removed |Added Target Milestone|--- |11.0 Resolution|---

[Bug c/95378] __atomic_load will write to objects of cv-qualified types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95378 Jonathan Wakely changed: What|Removed |Added Keywords||patch --- Comment #5 from Jonathan Wak

[Bug c/95378] __atomic_load will write to objects of cv-qualified types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95378 --- Comment #4 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:e40b11a91cb345db1324c3cb8f75b01e28056693 commit r11-1401-ge40b11a91cb345db1324c3cb8f75b01e28056693 Author: Jonathan Wakely Date:

[Bug c/95378] __atomic_load will write to objects of cv-qualified types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95378 --- Comment #3 from Jonathan Wakely --- GCC correctly refuses to write through const pointers for __atomic_test_and_set, __atomic_clear, and all of __atomic_fetch_op and __atomic_op_fetch.

[Bug c/95378] __atomic_load will write to objects of cv-qualified types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95378 --- Comment #2 from Jonathan Wakely --- Every __atomic_xxx built-in has the same problem. They'll all accept cv-qualified types as output parameters. This seems to fix it, but I'll finish testing it and submit it tomorrow: --- a/gcc/c-family/c-

[Bug c/95378] __atomic_load will write to objects of cv-qualified types

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95378 Jonathan Wakely changed: What|Removed |Added Ever confirmed|0 |1 Assignee|unassigned at gcc