public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Rennecke <amylaar@onetel.net.uk>
To: neil@daikokuya.demon.co.uk (Neil Booth)
Cc: amylaar@onetel.net.uk (Joern Rennecke),
	zack@codesourcery.com (Zack Weinberg),
	joseph@daikokuya.demon.co.uk, gcc@gcc.gnu.org
Subject: Re: Best way to remove cpp0
Date: Mon, 15 Oct 2001 01:18:00 -0000	[thread overview]
Message-ID: <200110150816.JAA06230@meolyon.local> (raw)
In-Reply-To: <20011015074042.B20594@daikokuya.demon.co.uk>

> Right; but that is precisely Joseph's suggestion, no?

No, he proposed to have a cc1 that writes the .i file while it is
simultanously - maybe with X tokens delay - compiling the preprocessing
tokens to assembler (or at least syntax check it with -fsyntax-only).

> > I can't follow you here.  Why is it posible to make a cc1-cum-cpp binary
> > with more efficient preprocessed output more easily than a single-purpose
> > cpp binary?
> 
> Because it is in cppmain.c, which uses the library's external
> interface.  If moved into the library, things that are currently done
> with function calls etc. could be done by derefencing pfile, for
> example.

Well, you could move the functionality into cpplib and have a separate cpp0
executable which just invokes that functionality.

      reply	other threads:[~2001-10-15  1:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 14:35 Neil Booth
2001-10-12 14:44 ` Daniel Jacobowitz
2001-10-12 15:24   ` Neil Booth
2001-10-12 14:48 ` Joseph S. Myers
2001-10-12 15:01 ` Stan Shebs
2001-10-12 15:19   ` Neil Booth
2001-10-14 17:45 ` Joern Rennecke
2001-10-14 23:41   ` Neil Booth
2001-10-15  1:18     ` Joern Rennecke [this message]

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=200110150816.JAA06230@meolyon.local \
    --to=amylaar@onetel.net.uk \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@daikokuya.demon.co.uk \
    --cc=neil@daikokuya.demon.co.uk \
    --cc=zack@codesourcery.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).