diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2024-01-23 19:59:00 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2024-01-23 19:59:00 +0100 |
| commit | dbc5f1f523b3cfa539d72fdd60b9479b3cd5a45d (patch) | |
| tree | 98be7c02df104a9be27e3c63f25a7f492cf17895 /MAINTAINERS | |
| parent | 06ee648e9bb8c121fbd93659f81d3380dba8be09 (diff) | |
| download | gcc-dbc5f1f523b3cfa539d72fdd60b9479b3cd5a45d.zip gcc-dbc5f1f523b3cfa539d72fdd60b9479b3cd5a45d.tar.gz gcc-dbc5f1f523b3cfa539d72fdd60b9479b3cd5a45d.tar.bz2 | |
c: Call c_fully_fold on __atomic_* operands in atomic_bitint_fetch_using_cas_loop [PR113518]
As the following testcase shows, I forgot to call c_fully_fold on the
__atomic_*/__sync_* operands called on _BitInt address, the expressions
are then used inside of TARGET_EXPR initializers etc. and are never fully
folded later, which means we can ICE e.g. on C_MAYBE_CONST_EXPR trees
inside of those.
The following patch fixes it, while the function currently is only called
in the C FE because C++ doesn't support BITINT_TYPE, I think guarding the
calls on !c_dialect_cxx () is safer.
2024-01-23 Jakub Jelinek <jakub@redhat.com>
PR c/113518
* c-common.cc (atomic_bitint_fetch_using_cas_loop): Call c_fully_fold
on lhs_addr, val and model for C.
* gcc.dg/bitint-77.c: New test.
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions