From: Martin Jambor <mjambor@suse.cz>
To: sameeran joshi <gsocsameeran@gmail.com>, gcc@gcc.gnu.org
Cc: Andi Kleen <ak@linux.intel.com>
Subject: Re: [GSoC 2019] [extending Csmith for fuzzing OpenMp extensions]
Date: Wed, 03 Apr 2019 16:50:00 -0000 [thread overview]
Message-ID: <ri6k1gbdodb.fsf@suse.cz> (raw)
In-Reply-To: <CAKz4L0HaGxFp6=_6UJbHjPJM2REKnj1_ztqOyKtOX_DaMwjKqA@mail.gmail.com>
Hello Joshi,
On Mon, Apr 01 2019, sameeran joshi wrote:
> HI,
> Discussing the project with Andi, I have drafted a proposal, please
> review and suggest
> necessary changes.
> If some OpenMP experts from GCC have some ideas or changes please suggest.
>
> https://docs.google.com/document/d/1axElw-I5pTwcjI4iMle5NhLeRCcshIjH5ZHm3GGwsZU/edit?usp=sharing
I will leave most of the evaluation on Andi (and assume he likes the
proposal, by the way). However, I have read the proposal, I like it and
I consider it very useful but also possibly quite ambitious. But we can
adjust expectations as we go forward.
Please consider fixing some of the formatting in the document,
especially of the code snippets, sometimes they are a bit difficult to
read without any indentation. That may be also the reason why I don't
quite understand what is the relationship of omp tasks and loops or
uninitialized local arrays.
But apart from that it is nice, thanks for applying,
Martin
next prev parent reply other threads:[~2019-04-03 16:50 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
2019-04-01 16:52 ` sameeran joshi
2019-04-01 17:02 ` sameeran joshi
2019-04-03 16:50 ` Martin Jambor [this message]
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=ri6k1gbdodb.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=ak@linux.intel.com \
--cc=gcc@gcc.gnu.org \
--cc=gsocsameeran@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).