From: Andi Kleen <ak@linux.intel.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: sameeran joshi <gsocsameeran@gmail.com>, gcc@gcc.gnu.org
Subject: Re: [GSoC 2019] [extending Csmith for fuzzing OpenMp extensions]
Date: Tue, 26 Mar 2019 13:32:00 -0000 [thread overview]
Message-ID: <20190326133214.GL18020@tassilo.jf.intel.com> (raw)
In-Reply-To: <20190326080550.GA7611@tucnak>
> That is a correct diagnostics.
>
> See Canonical loop form.
>
> test-expr One of the following:
> var relational-op b
> b relational-op var
>
> ( var relational-op b )
> is neither of those.
Still seems strange to fail for some meaningless brackets.
But ok.
-Andi
next prev parent reply other threads:[~2019-03-26 13:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 5:45 sameeran joshi
2019-02-18 18:22 ` Martin Jambor
2019-03-23 18:19 ` sameeran joshi
2019-03-24 2:55 ` Andi Kleen
2019-03-24 19:33 ` sameeran joshi
2019-03-26 0:41 ` Andi Kleen
2019-03-26 7:29 ` Jakub Jelinek
2019-03-26 8:00 ` sameeran joshi
2019-03-26 8:05 ` Jakub Jelinek
2019-03-26 13:32 ` Andi Kleen [this message]
2019-04-01 16:52 ` sameeran joshi
2019-04-01 17:02 ` sameeran joshi
2019-04-03 16:50 ` Martin Jambor
2019-04-03 17:46 ` sameeran joshi
2019-04-04 11:20 ` Martin Jambor
2019-04-04 13:45 ` sameeran joshi
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=20190326133214.GL18020@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=gcc@gcc.gnu.org \
--cc=gsocsameeran@gmail.com \
--cc=jakub@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).