Re: [Ctool-develop] testing the gcc test suite

[Shaun F. <fli...@so...>]

Hi Stefan,

I recently turned off the labels and extra debug output for the 
regression tests - I didn't bother fixing the gcc suite as it is not 
yet working.

Empty arrays are not allowed in Ansi C in general, it does seem like 
that should probably be a warning rather than an error though, since 
K&R C was lax about that.

The STDC thing is injected into the preprocessor on the line that calls 
cpp from project.cpp, some systems don't include it as yours apparently 
does, but it needs to be on to get many include files to function.

So, to sum up, don't worry about the gcc tests, they didn't run well 
before. :^)

Thanks,
Shaun

On Wednesday, September 3, 2003, at 05:45  AM, Stefan Seefeld wrote:

> hi there,
>
> I'm looking into the regression testing as I want
> to get that up and running again as a precondition
> for any non-trivial code changes. Specifically, I'm
> looking into the gcc test suite.
>
> Trying to compile the 'attrib' test, I run into
> various problems:
>
> * the file containing the expected output (run/attrib.out)
>   contains a lot more than the output generated by
>   the actual test run ('../../src/ctdemo run/attrib.c'),
>   i.e. symbol, tag, and label listings. It seems the
>   command used by the run_suite script isn't quite
>   complete. Adding '-d' will add most of the missing
>   stuff, though the listed names are mangled somehow,
>   they appear to contain the location in the source file
>   or something like that...
>
> * the run/attrib.c file compiled with my gcc (3.2.2)
>   generates a warning:
>
> run/attrib.c:14: Warning - old-style declaration or incorrect type:
>         __attribute__ ((__format__ (printf, 2, 3)));
>
>   Is that a recent addition to gcc ? Should that be fixed
>   in the ctool ? Or is there something else that can be
>   done to make this warning go away ?
>
>   The same warning is issued at various places with other
>   source files from that test suite as well.
>
> * /usr/include/gconf.h generates an error message:
>
> /usr/include/gconv.h:176: Unsized array not allowed as field:
>   __extension__ struct __gconv_step_data __data [];
>
>   Unfortunately I'm not a C expert, so I can't really comment
>   on this, other than that I see the line in gram.y that issues this
>   message. I'v no idea whether that's a gcc extension, or generally
>   how to deal with that.
>
> * once again the question concerning 'warning: "__STDC__" redefined':
>   what's causing this ? Does the ctdemo define and inject that macro
>   into the preprocessor ? It seems to be defined by my system (either
>   compiler or system headers or a combination thereof).
>
> I would hugely appreciate some help on getting this stuff up and 
> running,
> it would make it much easier to validate future code changes...
>
> Thanks a lot !
>
> 		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
>