public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Krishna Narayanan <krishnanarayanan132002@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Doubt regarding dg-directives
Date: Tue, 22 Feb 2022 14:32:57 +0000	[thread overview]
Message-ID: <CAH6eHdTarL-tB0PsZ3JWyoKDCzdDcbDVUZWZ0sPjc+qQsMWXKA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdS7wxLm=kyne=JO3HAd7bxnu6QeBaWaeTtZm-8QSP6fnQ@mail.gmail.com>

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.

  reply	other threads:[~2022-02-22 14:33 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 [this message]
2022-02-22 15:38     ` Krishna Narayanan
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=CAH6eHdTarL-tB0PsZ3JWyoKDCzdDcbDVUZWZ0sPjc+qQsMWXKA@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=krishnanarayanan132002@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).