public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Jan Madsen <Jan.Madsen@epfl.ch>
Cc: jbuck@synopsys.com, mark@markmitchell.com, egcs@cygnus.com,
	jason@cygnus.com
Subject: Re: Patch for sC++ to GNU C++.
Date: Sun, 25 Oct 1998 13:53:00 -0000	[thread overview]
Message-ID: <13228.909344584@hurl.cygnus.com> (raw)
In-Reply-To: <36304126.205C2B72@epfl.ch>

  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

  reply	other threads:[~1998-10-25 13:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-21  3:27 Jan Madsen
1998-10-21 19:20 ` Joe Buck
1998-10-22 11:32   ` Mark Mitchell
1998-10-22 18:00     ` Joe Buck
1998-10-22 21:15       ` Jan Madsen
1998-10-22 22:22       ` Mark Mitchell
1998-10-22 18:00         ` Joe Buck
1998-10-22 13:59           ` Mark Mitchell
1998-10-22 21:15             ` Joe Buck
1998-10-23  4:36               ` Jan Madsen
1998-10-25 13:53                 ` Jeffrey A Law [this message]
1998-10-22 21:15     ` Chip Salzenberg
1998-10-21 22:10 ` Mark Mitchell
     [not found] ` <199810212214.PAA16044.cygnus.egcs@smtp.earthlink.net>
1998-10-22 22:22   ` Jason Merrill
1998-10-25 18:03 ` Ken Raeburn
1998-10-22 13:59 Mike Stump
1998-11-13  5:01 Jan Madsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13228.909344584@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=Jan.Madsen@epfl.ch \
    --cc=egcs@cygnus.com \
    --cc=jason@cygnus.com \
    --cc=jbuck@synopsys.com \
    --cc=mark@markmitchell.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).