public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Shubham Narlawar <gsocshubham@gmail.com>
To: Martin Jambor <mjambor@suse.cz>, gcc@gcc.gnu.org
Cc: Martin Liska <mliska@suse.cz>
Subject: Re: GCC GSOC 2019
Date: Thu, 04 Apr 2019 11:26:00 -0000	[thread overview]
Message-ID: <CAN=hqDCdkekqkg8UbsaX2JKS0WUzHAZsqrftRSz_-exkVgvPaQ@mail.gmail.com> (raw)
In-Reply-To: <ri6mul7dp8z.fsf@suse.cz>

On Wed, Apr 3, 2019 at 10:01 PM Martin Jambor <mjambor@suse.cz> wrote:

> Hello Shubham,
>
> On Fri, Mar 29 2019, Shubham Narlawar wrote:
> > Hi, here is my proposal for the above idea. Please review and suggest
> > necessary changes.
> >
> >
> https://docs.google.com/document/d/11MNhuuD7dbwAfSW6ZgFrAys9My1Lw1PuMVcAqeNGr7A/edit?usp=sharing
>
> I have had a quick look and the proposal seems very nice.
>
> How did you select the attributes you want to implement in csmith?  It
> is for example a little strange that you decided to include "pure" but
> not "const."  If you handle visibility, you might as well consider
> throwing in externally_visible too, I guess.  As a stretch goal, the
> alias function attribute might be useful to exercise nasty paths in GCC
> IPA optimizations.
>

Thanks for the suggestion. I have added function attribute alias, const and
externally_visible in my proposal.
My bad, I forgot to add const.

Also, suggest some more attributes like alias which will help to exercise
different components of GCC, so that I can update my proposal accordingly.

>
> I assume Andi Kleen has seen this proposal and if he is fine with it, so
> am I.
>
Yes.

Thanks
Shubham


> Thanks,
>
> Martin
>
>

      parent reply	other threads:[~2019-04-04 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09 19:14 Shubham Narlawar
2019-02-18 18:26 ` Martin Jambor
2019-03-29  4:01   ` Shubham Narlawar
2019-04-03 16:31     ` Martin Jambor
2019-04-04  8:43       ` Martin Liška
2019-04-04 11:44         ` Shubham Narlawar
2019-04-05 12:07           ` Martin Liška
2019-04-07 13:00             ` Shubham Narlawar
2019-04-04 11:26       ` Shubham Narlawar [this message]

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='CAN=hqDCdkekqkg8UbsaX2JKS0WUzHAZsqrftRSz_-exkVgvPaQ@mail.gmail.com' \
    --to=gsocshubham@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    --cc=mliska@suse.cz \
    /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).