public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Iyer, Balaji V" <balaji.v.iyer@intel.com>
To: Jakub Jelinek <jakub@redhat.com>,
	"Joseph S. Myers"	<joseph@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"Aldy Hernandez (aldyh@redhat.com)" <aldyh@redhat.com>,
	Jeff Law <law@redhat.com>
Subject: RE: [GOMP4] [PATCH] SIMD-Enabled Functions (formerly Elemental functions) for C
Date: Tue, 19 Nov 2013 17:30:00 -0000	[thread overview]
Message-ID: <BF230D13CA30DD48930C31D4099330003A4A93BD@FMSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <20131119163125.GY892@tucnak.redhat.com>



> -----Original Message-----
> From: Jakub Jelinek [mailto:jakub@redhat.com]
> Sent: Tuesday, November 19, 2013 11:31 AM
> To: Joseph S. Myers
> Cc: Iyer, Balaji V; gcc-patches@gcc.gnu.org; Aldy Hernandez
> (aldyh@redhat.com); Jeff Law
> Subject: Re: [GOMP4] [PATCH] SIMD-Enabled Functions (formerly Elemental
> functions) for C
> 
> On Tue, Nov 19, 2013 at 04:13:34PM +0000, Joseph S. Myers wrote:
> > On Tue, 19 Nov 2013, Jakub Jelinek wrote:
> >
> > > Also, I wonder if you couldn't save the tokens wrapped into some
> > > tree temporarily into the attribute, rather than having to adjust
> > > c_parser_attribute callers.  Joseph, what do you prefer here?
> >
> > I think including whatever parsed data is relevant to this attribute
> > in the structure returned by c_parser_attributes (which is currently a
> > tree)
> 
> Well, it has to have an array of tokens, because it can't be parsed until the
> arguments of the function (which may come afterwards) are parsed.
> But IMHO it can be just created as vec<..., va_gc> of the tokens and pointer
> to that added to some magic tree code, or could be kept in an on-the-size
> data structure (say, put in an INTEGER_CST index into some vector inside of
> c_parser into the vector attribute argument temporarily, push the tokens
> into that vector and release it from the vector after parsing the function
> parameters (where OpenMP #pragma omp declare simd is parsed right
> now).
> That parsing then transforms it into a normal tree arguments.
> 

I just need a clarification, so I am sorry if I am making you repeat:

Right now, the array of tokens (vec<c_token> elem_fn_tokens) is passed in as a parameter and then passed back to the c_parser_declaration_or_fndef function.

Instead of that, you would like this information to be stored in parser->specs (using the c_parser_declspecs function) and then have my own routine that will go through these tokens and store them in the DECL_ATTRIBUTES (very similar to what c_finish_omp_declare_simd does).

Am I correct? Did I mistake anything?

Thanks,

Balaji V. Iyer.

> 	Jakub

  reply	other threads:[~2013-11-19 16:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  1:46 Iyer, Balaji V
2013-11-19  9:50 ` Jakub Jelinek
2013-11-19 16:17   ` Iyer, Balaji V
2013-11-19 16:46   ` Joseph S. Myers
2013-11-19 17:02     ` Jakub Jelinek
2013-11-19 17:30       ` Iyer, Balaji V [this message]
2013-11-19 17:33         ` Jakub Jelinek
2013-11-19 18:51           ` Iyer, Balaji V
2013-11-20  1:54           ` Iyer, Balaji V

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=BF230D13CA30DD48930C31D4099330003A4A93BD@FMSMSX101.amr.corp.intel.com \
    --to=balaji.v.iyer@intel.com \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=law@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).