This is the mail archive of the gcc@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: [tree-ssa] Building GENERIC trees cont.


> I've just checked out the tree-ssa-20020619-branch from CVS to make sure
> I've got a clean workspace. If a create a subdirectory <src>/gcc/bcpl and
> work from there, would I need to build gcc before I can start using the
> tree building functions?

Yes. Many target macros, and the garbage collection system is generated at 
build time.
By far the best solution is to teach the gcc build system about your frontend, 
and let that take care of everything. You should then be able to configure 
gcc with --enable-languages=bcpl.

This is [sort of] documented in "Anatomy of a Language Front End" in 
sourcebuild.texi. Of course the easiest solution is to cut/paste from the 
files in fortran/ or cp/

When I was doing the fortran frontend I created an empty frontend that was 
hardcoded to compile "void foo{return 0;}". Once this worked I started 
plugging in the actual frontend implementation. I'm afraid I never kept this 
skeleton frontend (actually there were several:).  It would have bitrotted 
beyond usefulness anyway.

Paul


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