This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: header.h vs. HEADER_H in dependencies


Volker Reichelt wrote:

> I could revert part of the change, i.e. replace $(VARRAY_H) in
> REGS_H and BASIC_BLOCK_H by varray.h again. (I'm just testing the
> patch. It survives bootstrap and the messages are gone. The
> testsuite is still running, though.)

Please do that, for now.  Let's not do over-much in this stage of the
development cycle.

I don't think you can really win here without automatically generated
dependencies.  The core problem is that the headers included by tm.h are
conditional on GENERATOR_FILE, but the Makefile is structured (using
$FOO_H dependencies) to assume that the set of dependencies is purely a
function of the header file.

(I thought moving cpplib to the top level was the change required to get
automatic dependencies working.  However, I'm not sure why even that is
required.  I would think that we could get with a Makefile that just
called out the vital dependencies (e.g., gen* dependent on first
building gen*.c, etc.).  If the compiler is being built with a non-GCC
compiler as the bootstrap compiler, just don't generate automatic
dependencies.  Then, editing stuff will not rebuild enough things.  But,
people who want to do serious development on GCC will always have a GCC
compiler around to use as the build compiler anyhow, in practice.)

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]