From: Christophe Lyon <christophe.lyon@linaro.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Tobias Burnus <tobias@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>
Subject: Re: [patch] OpenMP: Add -Wopenmp and use it
Date: Mon, 27 Nov 2023 11:20:20 +0100 [thread overview]
Message-ID: <CAPS5khYj3BtwaxahdL8YCr=xSub4vhhDm7us5XFHa+_ELsU+ng@mail.gmail.com> (raw)
In-Reply-To: <ZWCuS/RwelR8Q1iO@tucnak>
Hi!
On Fri, 24 Nov 2023 at 15:08, Jakub Jelinek <jakub@redhat.com> wrote:
>
> On Fri, Nov 24, 2023 at 02:51:28PM +0100, Tobias Burnus wrote:
> > Following the general trend to add a "[-W...]" to the warning messages
> > for both better grouping of the warnings and - more importantly - for providing
> > a means to silence such a warning (or to -Werror= them explicitly), this patch
> > replaces several '0' by OPT_Wopenmp.
> >
> > Comments or remarks before I commit it?
>
> LGTM, thanks for working on it.
>
> Jakub
>
I think the lack of final '.' in:
gcc/c-family/c.opt
+ Warn about suspicious OpenMP code
has caused the following regressions:
Running gcc:gcc.misc-tests/help.exp ...
FAIL: compiler driver --help=c option(s): "^ +-.*[^:.]$" absent from
output: " -Wopenmp Warn about suspicious OpenMP
code"
FAIL: compiler driver --help=c++ option(s): "^ +-.*[^:.]$" absent from
output: " -Wopenmp Warn about suspicious OpenMP
code"
FAIL: compiler driver --help=fortran option(s): "^ +-.*[^:.]$" absent
from output: " -Wopenmp Warn about suspicious
OpenMP code"
FAIL: compiler driver --help=warnings option(s): "^ +-.*[^:.]$" absent
from output: " -Wopenmp Warn about suspicious
OpenMP code"
I think you have received a notification from our CI about that?
Can you check it's as simple as that?
Thanks,
Christophe
next prev parent reply other threads:[~2023-11-27 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 13:51 Tobias Burnus
2023-11-24 14:08 ` Jakub Jelinek
2023-11-27 10:20 ` Christophe Lyon [this message]
2023-11-27 10:30 ` Jakub Jelinek
2023-11-27 10:33 ` Tobias Burnus
2023-11-27 15:06 ` Christophe Lyon
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='CAPS5khYj3BtwaxahdL8YCr=xSub4vhhDm7us5XFHa+_ELsU+ng@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=tobias@codesourcery.com \
/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).