On Wed, 10 Nov 2021, Tobias Burnus wrote:
> Cumulative update of the OpenMP 5.x changes in GCC 12.

Wow - quite a bit! 

> For the last bullet: the implementation-status documentation is new – 
> but even if it were not, linking to it makes sense. I kept adding and 
> removing a 'full' after the "The", which sounds better but while the 
> list in libgomp.texi is extensive, it does not have "full" coverage of 
> all changes. Additionally, as it is new, a "now" could be added after 
> "can".

gcc-12/changes.html: Update OpenMP status

       and the <code>affinity</code> clause are now supported and for Fortran
       additionally the following features which were available in C and C++
-      before:  <code>depobj</code>, <code>mutexinoutset</code> and

How about something like: "...supported. In addition Fortran gained...",
breaking up the long sentence?

+      <code>loop</code> directive and combined directives involving
+      <code>master</code> directive have been added.</li>

...involving the <code>master</code> directive 
             ^^^

+    <li>The following OpenMP 5.1 feature have been added: support for 
expressing

...features... (plural)

+      variable, the <code>reproducible</code> and <code>unconstrained</code>
+      modifiers to the <code>order</code> clause, and, for C/C++ only, the
+      align- and allocate-modifiers to the <code>allocate</code> clause and

<code>...</code> for align and allocate?

+      features and the <code>OMP_NUM_TEAMS</code> and
+      <code>OMP_TEAMS_THREAD_LIMIT</code> environement variables and their
+      associated API routines are now supported as well as the 
memory-allocation
+      routines added for Fortran and extended for C/C++ in OpenMP 5.1.

How about "...features. Finally..." or "...features. In addition..." to
break this long beast?

+      Fortran code, strictly-structured blocks can be used.</li>

Is there really a dash in "strictly structured"?

Hope this helps (and Jakub already approved, so please just consider
those additional suggestions).

Gerald

Reply via email to