Re: [Ctool-develop] testing the gcc test suite
Brought to you by:
flisakow
From: Shaun F. <fli...@so...> - 2003-09-04 16:23:42
|
Stefan, There is code inside lexer.l that turns "__builtin_va_list" into an ellipsis. There is code commented out there to turn it into an "int" instead. If it was made a builtin type like INT (defined near the top of gram.y) and had support inside printing, etc. it would work just like it always existed. __restrict doesn't appear to me to be a type, it looks like some sort of storage class modifier like extern or auto. I don't think we need to bother with a table of types, there are many gcc specifics which are not types, and still require handling, see the support for __attribute in lexer.l. I think gcc is popular enough these extensions may as well just be true built-ins in cTool. Thanks, Shaun On Wednesday, September 3, 2003, at 05:23 PM, Stefan Seefeld wrote: > hi there, > > I'm running into a series of other problems, which seem > at least partly to be gcc-specific: > > I see lines of the form: > > > typedef __builtin_va_list __gnuc_va_list; > > without any include directive including a file defining > '__builtin_va_list'. (of course not ! It's 'builtin'.) > > How can this be supported ? Should the ctool code set > up some internal table of predefined 'builtin' types / > identifiers ? > > Further, I'm seeing lots of declarations of the form: > > extern int _IO_vfscanf (_IO_FILE * __restrict, const char * __restrict, > _IO_va_list, int *__restrict) __THROW; > > i.e. with the keyword '__restrict'. This keyword isn't > recognized by the ctool parser either, so it reports > an error about 'duplicate parameter names'. > (In contrast to the first problem, the '__restrict' > keyword doesn't seem to be gcc-specific) > > Any suggestion how to fix this ? > > Thanks, > Stefan > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Ctool-develop mailing list > Cto...@li... > https://lists.sourceforge.net/lists/listinfo/ctool-develop > |