public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99303] OpenMP: typo in diagnostic
Date: Sun, 28 Feb 2021 10:17:58 +0000 [thread overview]
Message-ID: <bug-99303-4-n6GGep0UvR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99303-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99303
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:48ca2185bfb5126baacab812b3f14c80123ccb88
commit r11-7434-g48ca2185bfb5126baacab812b3f14c80123ccb88
Author: Jakub Jelinek <jakub@redhat.com>
Date: Sun Feb 28 11:16:33 2021 +0100
fortran: Fix up wording of 3 OpenMP diagnostic messages [PR99303]
As reported in the PR, some diagnostic messages need wording improvements.
2021-02-28 Jakub Jelinek <jakub@redhat.com>
PR fortran/99303
* openmp.c (gfc_omp_requires_add_clause): Fix up diagnostic message
wordings.
(resolve_omp_clauses): Likewise.
next prev parent reply other threads:[~2021-02-28 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 11:53 [Bug fortran/99303] New: " roland.illig at gmx dot de
2021-02-27 11:54 ` [Bug fortran/99303] " roland.illig at gmx dot de
2021-02-27 12:04 ` roland.illig at gmx dot de
2021-02-27 12:59 ` redi at gcc dot gnu.org
2021-02-27 14:51 ` jakub at gcc dot gnu.org
2021-02-28 10:17 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-28 10:19 ` jakub at gcc dot gnu.org
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=bug-99303-4-n6GGep0UvR@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).