On 22/09/14 14:30, James Greenhalgh wrote: > > On Thu, Sep 18, 2014 at 11:12:15AM +0100, Richard Earnshaw wrote: >> On 18/09/14 10:53, James Greenhalgh wrote: >>> +$(srcdir)/config/aarch64/aarch64-builtin-iterators.h: >>> $(srcdir)/config/aarch64/geniterators.sh \ >>> + $(srcdir)/config/aarch64/iterators.md >>> + $(SHELL) $(srcdir)/config/aarch64/geniterators.sh \ >>> + $(srcdir)/config/aarch64/iterators.md > \ >>> + $(srcdir)/config/aarch64/aarch64-builtin-iterators.h >>> + >>> aarch-common.o: $(srcdir)/config/arm/aarch-common.c $(CONFIG_H) >>> $(SYSTEM_H) \ >>> coretypes.h $(TM_H) $(TM_P_H) $(RTL_H) $(TREE_H) output.h $(C_COMMON_H) >>> $(COMPILER) -c $(ALL_COMPILERFLAGS) $(ALL_CPPFLAGS) $(INCLUDES) \ >>> >> >> Is there any real need to write this into the source directory and have >> the built file checked in? Ie. can't we always write to the build >> directory and use it from there. That avoids problems if the sources >> are on a read-only filesystem. >> >> If we do need to leave it in the sources, then contrib/update_gcc should >> be taught how to touch the generated file when resyncing from the >> repositories. >> > > I thought I had tried this and failed to make it work. I must not have > been trying hard enough at the time. > > Updated as attached, generating the header in the build directory. It > looks much better this way! > > Bootstrapped on aarch64-none-linux-gnueabi with no issues. > > Ok? > > Thanks, > James > > --- > gcc/ > > 2014-09-22 James Greenhalgh <james.greenha...@arm.com> > > * config/aarch64/geniterators.sh: New. > * config/aarch64/iterators.md (VDQF_DF): New. > * config/aarch64/t-aarch64: Generate aarch64-builtin-iterators.h. > * config/aarch64/aarch64-builtins.c (BUILTIN_*) Remove. > >
OK. R.
