[GOMP4] [PATCH] SIMD-Enabled Functions (formerly Elemental functions) for C

Iyer, Balaji V balaji.v.iyer@intel.com
Tue Nov 19 18:51:00 GMT 2013



> -----Original Message-----
> From: Jakub Jelinek [mailto:jakub@redhat.com]
> Sent: Tuesday, November 19, 2013 12:00 PM
> To: Iyer, Balaji V
> Cc: Joseph S. Myers; 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:54:29PM +0000, Iyer, Balaji V wrote:
> > 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
> > parser->own
> 
> No, somewhere in *parser, it can be a new field with vector of the
> vec<c_token, va_gc> vectors or similar and store something that can be used
> to find that out into vector attribute argument.  Then at the spot where the
> #pragma omp declare simd tokens are parsed right now (when arguments
> are finally available) you could look up the vector attribute and parse the
> corresponding tokens.
> 

Thanks for helping me with this! I guess this is similar to what you are doing in C++.

Is it OK if I store the entire token list of vectors? It is not a lot of tokens and it is only there for a short period of time, and will release it as soon as I am done with it.

-Balaji V. Iyer.


> 	Jakub



More information about the Gcc-patches mailing list