public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@apple.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Zack Weinberg <zack@codesourcery.com>,
	joseph@daikokuya.demon.co.uk, gcc@gcc.gnu.org
Subject: Re: Best way to remove cpp0
Date: Fri, 12 Oct 2001 15:01:00 -0000	[thread overview]
Message-ID: <3BC76795.34CF262E@apple.com> (raw)
In-Reply-To: <20011012223509.A30940@daikokuya.demon.co.uk>

Neil Booth wrote:
> 
> However, if there's a bug in the compiler during 2), say a segfault,
> then the preprocessed output with -save-temps would only proceed as
> far as the compiler bug.  We have asked users to submit the
> preprocessed output obtained with -save-temps.
> 
> What's the best way forwards for this case?

How much overhead would it be to buffer all the way to the end of
a file, and write out before proceeding to compilation proper?
When a segfault occurs, things are going to be pretty scrambled,
you'll want your tokens safe on disk.

Or you could have -save-temps read ahead by a half-million tokens
or so, then dump before proceeding into compilation proper.  You
can prevent bloat (although -save-temps is something you use when
you're desperate to debug and not caring much about size/speed),
but still most .i files will be complete and well-formed.

Stan

  parent reply	other threads:[~2001-10-12 15:01 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 [this message]
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

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=3BC76795.34CF262E@apple.com \
    --to=shebs@apple.com \
    --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).