From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hamza.pair.com (hamza.pair.com [209.68.5.143]) by sourceware.org (Postfix) with ESMTPS id B2FAF3858408 for ; Wed, 10 Nov 2021 23:12:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B2FAF3858408 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pfeifer.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=pfeifer.com Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id 3D12B33F04; Wed, 10 Nov 2021 18:12:32 -0500 (EST) Received: from naga.dhcp.nue.suse.com (nat1.nue.suse.com [195.135.221.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hamza.pair.com (Postfix) with ESMTPSA id 90A9233EFE; Wed, 10 Nov 2021 18:12:31 -0500 (EST) Date: Thu, 11 Nov 2021 00:12:31 +0100 (CET) From: Gerald Pfeifer To: Tobias Burnus cc: gcc-patches , Jakub Jelinek Subject: Re: [wwwdocs, patch] gcc-12/changes.html: Update OpenMP status In-Reply-To: Message-ID: References: MIME-Version: 1.0 X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2021 23:12:34 -0000 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 affinity clause are now supported and for Fortran additionally the following features which were available in C and C++ - before: depobj, mutexinoutset and How about something like: "...supported. In addition Fortran gained...", breaking up the long sentence? + loop directive and combined directives involving + master directive have been added. ...involving the master directive ^^^ +
  • The following OpenMP 5.1 feature have been added: support for expressing ...features... (plural) + variable, the reproducible and unconstrained + modifiers to the order clause, and, for C/C++ only, the + align- and allocate-modifiers to the allocate clause and ... for align and allocate? + features and the OMP_NUM_TEAMS and + OMP_TEAMS_THREAD_LIMIT 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.
    • Is there really a dash in "strictly structured"? Hope this helps (and Jakub already approved, so please just consider those additional suggestions). Gerald