From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F0AC7385B53B; Wed, 8 Feb 2023 23:15:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F0AC7385B53B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675898118; bh=Uw84cx7uZLY8w55/ZYSPz0eUIMLpd+GAZ3FN5HKC57w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JbpYuBQRdJJUbkSyg6w4P2O0H/rr5CNGh7a3MdbNzt/Yim/drIO0Wz09aOLSJbUte OkzEhS4ZljSU++PLBkFNVDXeFD1rObrfYX4wxkV4D6kBGMrS4MWq2cSLS4n1a9iTRt 0Tjs3w9bjizGldq6B7Jzswv3yHJw9KYP5YLEFS/M= From: "matt at immute dot net" To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/108732] Pre-compiled headers cannot be output to /dev/null Date: Wed, 08 Feb 2023 23:15:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: pch X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: matt at immute dot net X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108732 --- Comment #7 from Matt Hellige --- Those make sense as internal details. I don't think a typical user should be expected to guess or learn these differences in order to use the GCC from t= he command line. So, whether or not they suffice as justification for a command failing when it always worked with prior versions, I suppose will be a matt= er of taste.=