From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 38FA53858D39; Wed, 8 Feb 2023 22:23:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 38FA53858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1675895001; bh=kcQT8rI7/IuvE1gqe+ab70z8d5CwNbr+Hkmsiax+j5M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=M8OqakzZMvy5M2ZEtTqeLkp5eaaqHgnokwIYHoohbteY3QL3JZMcYqTKB0oMBLBSo KNgEIBBaYTgIfoq/LHGrYOLP5Ot89htOK1Rjyqa9LxrAfjwd4unkoKUbx9jhTrnP0Y LUAI/4ESTi3FQO3CjNpa3P37T2ka45mpEleL7aEE= 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 22:23:20 +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 #3 from Matt Hellige --- As long as I'm updating builds, I'll switch to that invocation, thanks. I still do think it's a little odd that in this case (and *only* in this ca= se?) output needs to be written to a mappable file. That does not seem to be a typical implication of a -o flag of any tool I've ever used. And in fact your suggested change sort of proves my point... Why would a us= er suspect that /dev/null can be used for both input and output of that gcc -xc invocation, but not the other one?=