https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101274
Thomas Rodgers <rodgertq at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Thomas Rodgers <rodgertq at gcc dot gnu.org> --- The standard only requires that the the parallel algorithm's execution, when invoked with std::sequenced_policy, be invoked on the calling thread, and (as with the other execution policies) allows for the invocations of element access functions to be indeterminately sequenced on the execution agent. This is also spelled at - https://en.cppreference.com/w/cpp/algorithm/execution_policy_tag_t "1) The execution policy type used as a unique type to disambiguate parallel algorithm overloading and require that a parallel algorithm's execution may not be parallelized. The invocations of element access functions in parallel algorithms invoked with this policy (usually specified as std::execution::seq) are indeterminately sequenced in the calling thread."