This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: request for timings - makedepend
Tom Tromey <tromey@redhat.com> writes:
> >>>>> "Zack" == Zack Weinberg <zack@codesourcery.com> writes:
>
> >> Computed headers are dealt with somewhat clumsily in automake. As a
> >> user you specify "BUILT_SOURCES", and then these are built by 'all'
> >> before anything else is done.
>
> Zack> This might not be all that bad in gcc land. It's good to generate all
> Zack> the generated sources up front, because certain of them tend to
> Zack> bottleneck a parallel build anyway (I think you know which ones I
> Zack> mean). One problem I see is that the set of gt-*.h files is large and
> Zack> cannot be easily determined up front.
>
> Personally I wouldn't have a problem just requiring them to be listed
> in a variable in Make-lang.in. If you add a new '#include
> "gt-blah.h"', then you add a new line to Make-lang.in. (But then,
> gcjx only has two gt-*.h files... so it is no big deal for me.)
>
>
> Right now the Makefiles have things like this:
>
> gt-java-hooks.h gt-java-langhooks.h : s-gtype ; @true
>
> We could just replace this with:
>
> $(all_gt_h_files) : s-gtype ; @true
>
> ... meaning that the only difference to the maintainer is where the
> file gets listed.
You could even have gengtype simply put a list of the files that it
generated, and the files that should depend on them, into a .d file.
Then you wouldn't have to have the list at all, and there'd be one
less step in the 'I added the first GTY to a file' process.