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]

Re: Patch for sC++ to GNU C++.



  In message <36304126.205C2B72@epfl.ch>you write:
  > I will put my extension into a separate directory. However, I would very
  > much like to hear the opinion of Jason or Jeff concerning this work and
  > to know which version of GCC a patch should be made against.
Well, front-ends are probably my weakest area in the compiler itself, and it
only gets worse for languages like C++ which I don't know or understand :-)

>From a high level I'd have the same concerns that other folks have expressed.
Primarily that we don't want to duplicate a lot of code.  The other concern
is we don't want to bludgeon the C++ front end too much and make life too
difficult on the folks working on our C++ compiler.

In the end, Jason and the other folks working on the C++ front end will have
to decide which side of the fence to fall on.

Note that you'll need to deal with the copyright assignment issues before any
of this work can be integrated.

  > There is, however, a couple of things I do not know how to do. If you
  > could explain to me how it is done and/or point me to the places where a
  > similar thing is done it will ease my task very much. First, can you
  > point me to the place where the 'sed' command manipulates the c-parse.in
  > file.
I'd look in objc/Makefile.in and objc/Make-lang.in

  >  Second, I have modified the file cp/lang-specs.h to accept the
  > extensions '.scc' and '.scxx', where does this change go (into the gcc
  > main program? how?)?
gcc.c?  Maybe?  I'm not good with the spec stuff either (can you tell my
background is optimizers and backends :-)

jeff


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