https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97655
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Guess the second condition should be !c->capture. The spec says that atomic_default_mem_order(acq_rel) makes mem-order-clause default to acquire for read, acq_rel for capture and release otherwise - write or update or atomic-clause missing. Now, something I have clearly missed in the review, why is capture not part of atomic_op? capture is atomic-clause like the others. And I'd be afraid we'd allow something like !$omp atomic capture update or !$omp atomic update capture by making it separate.
