From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Zack Weinberg <zackw@Stanford.EDU>, gcc@gcc.gnu.org
Subject: Re: cpplib: Nix -g3.
Date: Wed, 10 Jan 2001 13:38:00 -0000 [thread overview]
Message-ID: <20010110211105.B21420@daikokuya.demon.co.uk> (raw)
In-Reply-To: <20010110041336.V1120@devserv.devel.redhat.com>
Jakub Jelinek wrote:-
> BTW: cpp0 -g3 (nor cpp0 -dD) omits the builtin macros and macros specified
> on the command line in the output (this got broken during the last lexer
> rewrite).
You're not really supposed to invoke cpp0 directly.
But, yes, cppmain does ignore those regardless of how it's invoked. I
thought it was intentional - it's been in cppmain.c for a while.
This were causing me a minor headache, in fact, for making cpp_reader
opaque - I'd be quite happy to get rid of it and output the lot - if
Zack has no objections.
It's caused by the condition
if (pfile->done_initializing)
{
[...]
}
in cb_define and cb_undef of cppmain.c.
Neil.
next parent reply other threads:[~2001-01-10 13:38 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 [this message]
2001-01-10 15:46 ` Zack Weinberg
2001-01-10 15:59 ` Neil Booth
2001-01-11 0:57 ` Zack Weinberg
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=20010110211105.B21420@daikokuya.demon.co.uk \
--to=neil@daikokuya.demon.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=zackw@Stanford.EDU \
/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).