From: Krishna Narayanan <krishnanarayanan132002@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Doubt regarding dg-directives
Date: Tue, 22 Feb 2022 21:08:40 +0530 [thread overview]
Message-ID: <CABhGnjtsuKD=RzaQkuo2W2ozGjJCO1iU510B=CMJDebY5wX24w@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdTarL-tB0PsZ3JWyoKDCzdDcbDVUZWZ0sPjc+qQsMWXKA@mail.gmail.com>
Yes, it does.
I used dg-warning and not dg warning (that was a sheer typing mistake).
The warning is about the uninitialized variable being used in the
testcase yet there is no warning on that line and the test results in
FAIL.
I used /* { dg-warning "uninitialized" } */ on that particular line.I
used the test in gcc.dg, with other directive /* { dg-options "-O2" }
*/ .
Can you help me where I went wrong?
Thanks,
Krishna Narayanan
On Tue, Feb 22, 2022 at 8:03 PM Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>
>
>
> On Tue, 22 Feb 2022 at 14:31, Jonathan Wakely wrote:
>>
>>
>>
>> On Tue, 22 Feb 2022 at 11:43, Krishna Narayanan via Gcc-help <gcc-help@gcc.gnu.org> wrote:
>>>
>>> Hello,
>>> I had been working on a testcase,in which there had to be a warning on
>>> a specific line. On giving the /* { dg warning "text" } */ to that
>>
>>
>>
>> That should be dg-warning, did you get it right in the test?
>>
>>>
>>> line ,the test outcome is FAIL(test for warnings) even though the
>>> warning was expected.
>
>
> And does the warning actually happen? dg-warning says a warning is expected, so the test will fail if no warning happens.
>
>
next prev parent reply other threads:[~2022-02-22 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 11:42 Krishna Narayanan
2022-02-22 14:31 ` Jonathan Wakely
2022-02-22 14:32 ` Jonathan Wakely
2022-02-22 15:38 ` Krishna Narayanan [this message]
2022-02-22 15:44 ` Segher Boessenkool
2022-02-22 18:30 ` Krishna Narayanan
2022-02-23 0:32 ` Segher Boessenkool
2022-02-22 16:14 ` Jonathan Wakely
2022-02-23 7:39 ` Krishna Narayanan
2022-02-23 8:16 ` Jonathan Wakely
2022-02-23 13:47 ` Krishna Narayanan
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='CABhGnjtsuKD=RzaQkuo2W2ozGjJCO1iU510B=CMJDebY5wX24w@mail.gmail.com' \
--to=krishnanarayanan132002@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).