On Tue, Sep 07, 2021 at 06:07:35PM +0200, Tobias Burnus wrote:
> > depend case from the other clauses. The depend parsing tries to parse it
> > as the rigid varname followed by optional . field or array section and if
> > that fails, parses it as an expression, verifies it is lvalue and just
> > uses the address of that lvalue as the depend address.
> Is this okay (Y) – or should be better improved (P + comment)? I did use
> "Y".
Let's go with Y.
> > While for map/to/from, I think what we need to do is make the OpenMP array
> > section a new tree code (perhaps C/C++ FE only), ...
> Now split off and marked as "N".
>
> I did look through some lists – and found range-based for loops (Y) as
> item not in Appendix B. (And fixed one typo)
Bronis didn't want that bullet because there was C++11/C++14 support bullet
and he argued that range based for loops falls into that.
But IMHO range for is significant change that is worth explicit bullet.
> libgomp.texi: Extend OpenMP 5.0 Implementation Status
>
> libgomp/
> * libgomp.texi (OpenMP Implementation Status): Extend
> OpenMP 5.0 section.
> (OpenACC Profiling Interface): Fix typo.
Ok, thanks.
Jakub
