From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27858 invoked by alias); 29 Nov 2003 23:21:16 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 27829 invoked from network); 29 Nov 2003 23:21:12 -0000 Received: from unknown (HELO kraid.nerim.net) (62.4.16.106) by sources.redhat.com with SMTP; 29 Nov 2003 23:21:12 -0000 Received: from tetto.gentiane.org (espie.gentiane.org [62.212.102.210]) by kraid.nerim.net (Postfix) with ESMTP id DE60D4185D; Sun, 30 Nov 2003 00:21:09 +0100 (CET) Received: from tetto.gentiane.org (espie@localhost [127.0.0.1]) by tetto.gentiane.org (8.12.9/8.12.1) with ESMTP id hATNL98m032459; Sun, 30 Nov 2003 00:21:09 +0100 (CET) Received: (from espie@localhost) by tetto.gentiane.org (8.12.9/8.12.1/Submit) id hATNL7Ts001901; Sun, 30 Nov 2003 00:21:08 +0100 (CET) Date: Sun, 30 Nov 2003 00:15:00 -0000 From: Marc Espie To: Neil Booth Cc: Andreas Schwab , gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: PATCH: work-around for bug in -traditional-cpp Message-ID: <20031129232107.GA4998@tetto.gentiane.org> Reply-To: espie@nerim.net References: <20031125125336.GA3717@tetto.gentiane.org> <20031129154742.GA17134@tetto.gentiane.org> <20031129215042.GA18674@daikokuya.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031129215042.GA18674@daikokuya.co.uk> User-Agent: Mutt/1.4.1i X-SW-Source: 2003-11/txt/msg02326.txt.bz2 On Sat, Nov 29, 2003 at 09:50:42PM +0000, Neil Booth wrote: > > > > Okay, it looks like trad-cpp is messing with skipping. > > If you're skipping you shouldn't even be attempting to expand > macros. Yes, sure. But I don't think trad-cpp knows whether it's skipping at this point. It does expand macros early, and then it will use them or discard them when it finds out whether it's skipping or not. This is not my code. I'm only concerned about not getting warnings when I should not get any, e.g., make the code work. If you can figure what's actually going on, and can clean it up, that will be fine.