From: Christophe Lyon <christophe.lyon@linaro.org>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Marek Polacek <polacek@redhat.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH c/c++] use explicit locations for some warnings in c-pragma.c
Date: Mon, 21 Sep 2015 00:33:00 -0000 [thread overview]
Message-ID: <CAKdteOa0O4zczPTcsbgAOvjH9f+NLit-0-KGqKN-g1snDcfnjA@mail.gmail.com> (raw)
In-Reply-To: <CAESRpQCA152OU=ejAq_JN2uzArKAMxR0DX_gGAUCjvo+JvWwAg@mail.gmail.com>
On 21 September 2015 at 02:24, Manuel López-Ibáñez
<lopezibanez@gmail.com> wrote:
> On 21 September 2015 at 02:22, Christophe Lyon
> <christophe.lyon@linaro.org> wrote:
>> It works for me if I replace 24 by 62.
>
> Wierd. What is the actual output of the compiler?
Here is what I have in gcc.log:
/home/christophe.lyon/src/GCC/sources/gcc-fsf/trunk/gcc/testsuite/gcc.dg/pragma-diag-5.c:2:62:
warning: missing [error|warning|ignored|push|pop] after '#pragma GCC
diagnostic' [-Wpragmas]^M
/home/christophe.lyon/src/GCC/sources/gcc-fsf/trunk/gcc/testsuite/gcc.dg/pragma-diag-5.c:5:24:
warning: expected [error|warning|ignored|push|pop] after '#pragma GCC
diagnostic' [-Wpragmas]^M
/home/christophe.lyon/src/GCC/sources/gcc-fsf/trunk/gcc/testsuite/gcc.dg/pragma-diag-5.c:7:32:
warning: unknown option after '#pragma GCC diagnostic' kind
[-Wpragmas]^M
XPASS: gcc.dg/pragma-diag-5.c missing (test for warnings, line 2)
PASS: gcc.dg/pragma-diag-5.c (test for warnings, line 5)
PASS: gcc.dg/pragma-diag-5.c (test for warnings, line 7)
PASS: gcc.dg/pragma-diag-5.c (test for excess errors)
next prev parent reply other threads:[~2015-09-21 0:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 17:47 Manuel López-Ibáñez
2015-05-25 19:48 ` Jason Merrill
2015-05-25 20:17 ` Marek Polacek
2015-05-25 20:55 ` Manuel López-Ibáñez
2015-09-20 20:38 ` Christophe Lyon
2015-09-20 22:35 ` Manuel López-Ibáñez
2015-09-21 0:24 ` Christophe Lyon
2015-09-21 0:29 ` Manuel López-Ibáñez
2015-09-21 0:33 ` Christophe Lyon [this message]
2015-09-21 1:46 ` Manuel López-Ibáñez
2015-09-21 5:50 ` Christophe Lyon
2015-09-21 12:32 ` Manuel López-Ibáñez
2015-11-04 9:46 ` Mike Stump
2015-11-04 21:02 ` Manuel López-Ibáñez
2015-11-06 21:16 ` Mike Stump
2015-11-06 21:18 ` Mike Stump
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=CAKdteOa0O4zczPTcsbgAOvjH9f+NLit-0-KGqKN-g1snDcfnjA@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=lopezibanez@gmail.com \
--cc=polacek@redhat.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).