public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Zack Weinberg" <zackw@Stanford.EDU>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc@gcc.gnu.org
Subject: Re: cpplib: Nix -g3.
Date: Thu, 11 Jan 2001 00:57:00 -0000	[thread overview]
Message-ID: <20010111005714.V2032@wolery.stanford.edu> (raw)
In-Reply-To: <20010110235853.G21420@daikokuya.demon.co.uk>

On Wed, Jan 10, 2001 at 11:58:53PM +0000, Neil Booth wrote:
> Zack Weinberg wrote:-
> 
> > There was a very good reason for this which I don't remember anymore.
> > I think it might have had to do with the printer not being set up
> > early enough, so it would crash.
> 
> I think you might be right about the printing.  Anyway, that problem
> is no more.  Cool, another kludge we can eliminate.
> 
> The only issue is where this stuff shows up the in preprocessed output
> - the line numbering might be screwy, giving problems with a re-read
> and -fpreprocessed.  Maybe that was a reason?

That too might've been something to do with.  IIRC we're supposed to
spit out 

# 1 "file.c"

in between each builtin macro definition.  1 might have been 0.  This
was a very long time ago.

zw

  reply	other threads:[~2001-01-11  0:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010109233506.C7013@daikokuya.demon.co.uk>
     [not found] ` <20010109155204.A2032@wolery.stanford.edu>
     [not found]   ` <20010110000706.C10605@daikokuya.demon.co.uk>
     [not found]     ` <20010110041336.V1120@devserv.devel.redhat.com>
2001-01-10 13:38       ` Neil Booth
2001-01-10 15:46         ` Zack Weinberg
2001-01-10 15:59           ` Neil Booth
2001-01-11  0:57             ` Zack Weinberg [this message]
2001-01-11 10:54               ` Neil Booth
2001-01-11 20:41                 ` Zack Weinberg
2001-01-14 11:52                 ` Jason Merrill
2001-01-14 11:59                   ` Neil Booth
2001-01-15  4:14                     ` Jason Merrill
2001-01-12  5:50 David Korn
2001-01-12 14:23 ` Neil Booth

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=20010111005714.V2032@wolery.stanford.edu \
    --to=zackw@stanford.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=neil@daikokuya.demon.co.uk \
    /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).