From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.killthe.net (unknown [207.126.114.3]) by sourceware.org (Postfix) with ESMTP id 6D79A3858C56 for ; Tue, 21 Jun 2022 12:56:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6D79A3858C56 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=killthe.net Authentication-Results: sourceware.org; spf=none smtp.mailfrom=killthe.net Received: from magic (unknown [166.196.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.killthe.net (Postfix) with ESMTPSA id 653261205A5; Tue, 21 Jun 2022 08:56:58 -0400 (EDT) Date: Tue, 21 Jun 2022 07:57:52 -0500 From: Dave Blanchard To: Richard Biener Cc: gcc@gcc.gnu.org Subject: Re: Change in preprocessor behavior Message-Id: <20220621075752.d356377f0406b6622764ae4e@killthe.net> In-Reply-To: References: <20220620193418.37581569f8a43bbaded229e6@killthe.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2022 12:57:01 -0000 On Tue, 21 Jun 2022 09:28:00 +0200 Richard Biener wrote: > On Tue, Jun 21, 2022 at 2:34 AM Dave Blanchard wrote: > > > > At some point between GCC 9 and GCC 12, the preprocessor started behaving differently. Before if GCC were launched as /lib/cpp or /usr/bin/cpp (I think) it would assume the user wanted to preprocess something and automatically launch in preprocessor mode. Now the behavior has changed and it just acts as the normal compiler. Can someone kindly point me to the patch or commit where this feature was changed, and the rationale for doing so? Thank you. > > maybe you can be more specific as to how you invoke 'cpp'. Did you > build gcc yourself? What > is the 'cpp' you invoke (is it maybe a script or a symlink?) Oops, it looks like my script had accidentally overwritten 'cpp' with a symlink to gcc. Fixed that and it's working now. Thanks.