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]

naming convention for cc1, cc1plus, etc.


Hi,

What name should I give the executable for the Mercury front-end?
`cc1mercury'?  `mc1'?  `gcc_mercury_compile'?

The `toy' example uses `cc1toy', but the Java front-end uses `jc1',
which seems to make more sense (it stands for "java compiler pass 1",
right?).

And should it go in the top-level directory, or in the `mercury'
subdirectory?  The toy example puts cc1toy in the `toy' subdirectory,
but all the other front-ends put it in the main gcc directory,
alongside xgcc.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the pursuit
                                    |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.

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