From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) by sourceware.org (Postfix) with ESMTPS id 3D14C3857B86 for ; Tue, 21 Jun 2022 19:48:02 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3D14C3857B86 Received: by mail-wm1-x333.google.com with SMTP id x6-20020a1c7c06000000b003972dfca96cso7795914wmc.4 for ; Tue, 21 Jun 2022 12:48:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=y2FeQuo5ZQ+ArCyINcg8EyL28gsrRVQmX1WrzzchASY=; b=KQ80QhTnvQ1FzLaTvzCj627+N78kqqQmq+JP92YrZ0LJ4OpffQxXV7oSBMCoYJM5LB ro9qaFVDjWaOXvXdlPFaauHnrd7fY3Bnw0vW1yC8DR9FHas8YADfh9pqHLcJtokQaMcY MuTniOvdwNC5gpAaJNohgfdrekU4it96sS29zYT1buMjdanl+IflKn/HtDAl5lCIw4Sa y6u0r2wEBWPcVmN4UM10DTUfU/oiTIB7LiXWYVpnuwcMzbvZ091PTYB5NkHiMgy8BYD/ wjsuLGU952JGrmhLRT6t6RRLCLO9SW7UaFAaBDsSwlRnSh8jdcGYCdWAfbyxMy5jVGvh bWgw== X-Gm-Message-State: AJIora8uAUU0iPNn7tkmiLdqgYKFevnabSdmuMl5KANHcMmAGv+N7fYD RHIGhFyXnWLld+AXCUrGqDBXrpIG7GOvurahbqI= X-Google-Smtp-Source: AGRyM1tLoDgHQGB4fVg0EA/TrBa9yzc4eFBLZxi2y9vyRbUqKcsmU6GGQ+lXc7UhOLLqPGdg5XR63bGwYN+4qT/cfsA= X-Received: by 2002:a7b:c755:0:b0:39c:3beb:32aa with SMTP id w21-20020a7bc755000000b0039c3beb32aamr32419502wmk.30.1655840880919; Tue, 21 Jun 2022 12:48:00 -0700 (PDT) MIME-Version: 1.0 References: <25266.7279.168888.944211@thutt-l01.ddns.vmware.com> In-Reply-To: From: Jonathan Wakely Date: Tue, 21 Jun 2022 20:47:49 +0100 Message-ID: Subject: Re: Narrowing down preprocessor-related potential defect To: thutt Cc: "gcc@gcc.gnu.org" X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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 19:48:04 -0000 On Tue, 21 Jun 2022, 20:35 Jonathan Wakely, wrote: > On Tue, 21 Jun 2022 at 20:31, thutt--- via Gcc wrote: > > I am here to solicit ideas on how to further narrow this this > > down. Is there any undocumented option that I can use to cause the > > standalone preprocessor to produce output identical to input? > > Note that '-traditional-cpp' does not work because some of the code > > is not recognized (variadic macros, for example). > > This seems off-topic for the gcc mailing list. It belongs on the gcc-help > list. > > Have you tried not using a standalone preprocessor? > > The usual approach is to add -save-temps to the gcc invocation, so it > leaves the preprocessed output in a separate .i file. > > N.B. it's a warning, not an error. You told GCC to turn that warning > into an error. > GCC has a whole guide to test case reduction here: https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction I don't know how much will be applicable it usable in this instance.