From: Neil Booth <neil@daikokuya.co.uk>
To: Marc Espie <espie@nerim.net>
Cc: Andreas Schwab <schwab@suse.de>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: PATCH: work-around for bug in -traditional-cpp
Date: Sat, 29 Nov 2003 23:11:00 -0000 [thread overview]
Message-ID: <20031129215042.GA18674@daikokuya.co.uk> (raw)
In-Reply-To: <20031129154742.GA17134@tetto.gentiane.org>
Marc Espie wrote:-
> On Tue, Nov 25, 2003 at 02:27:50PM +0100, Andreas Schwab wrote:
> > An even simpler test case:
> >
> > #define a(b,c)
> > #if 0
> > #define b(x,y) a(x)
> > #endif
> >
> > cpp.c:3: macro "a" requires 2 arguments, but only 1 given
> >
> > Interestingly, changing #if 0 to #if 1 removes the error.
>
> Okay, it looks like trad-cpp is messing with skipping.
If you're skipping you shouldn't even be attempting to expand
macros.
Neil.
next prev parent reply other threads:[~2003-11-29 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-25 15:31 Bug in traditional cpp in gcc 3.3.2 ? Marc Espie
2003-11-25 17:01 ` Andreas Schwab
2003-11-29 18:14 ` PATCH: work-around for bug in -traditional-cpp Marc Espie
2003-11-29 23:11 ` Neil Booth [this message]
2003-11-29 23:52 ` Marc Espie
[not found] <bqb9lu$m85$2@clipper.ens.fr>
2003-12-07 18:30 ` Marc Espie
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=20031129215042.GA18674@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=espie@nerim.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=schwab@suse.de \
/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).