public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Damian Rouson <damian@sourceryinstitute.org>
To: gcc patches <gcc-patches@gcc.gnu.org>
Cc: gfortran <fortran@gcc.gnu.org>
Subject: [wwwdocs] Add GCC 8 Fortran feature description
Date: Wed, 02 May 2018 18:22:00 -0000	[thread overview]
Message-ID: <etPan.5aea01c9.7d3e6683.6012@sourceryinstitute.org> (raw)

The patch below includes a description of a new feature in gfortran for inclusion in the GCC 8 changes.html file.  I don’t have commit rights.  Could someone approve and apply this?  Thanks.

Damian


cvs diff: Diffing .
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.74
diff -r1.74 changes.html
761a762,765
>   <li> 
>     Partial support is provided for Fortran 2018 teams, which are hierarchical
>     subsets of images that execute independently of other image subsets. 
>   </li>

             reply	other threads:[~2018-05-02 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 18:22 Damian Rouson [this message]
2018-05-13 17:34 ` Damian Rouson
2018-05-17  6:32 ` Thomas Koenig
2018-05-17 12:22   ` Damian Rouson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=etPan.5aea01c9.7d3e6683.6012@sourceryinstitute.org \
    --to=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).