public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matt at immute dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108732] New: Pre-compiled headers cannot be output to /dev/null Date: Wed, 08 Feb 2023 21:59:34 +0000 [thread overview] Message-ID: <bug-108732-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108732 Bug ID: 108732 Summary: Pre-compiled headers cannot be output to /dev/null Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: matt at immute dot net Target Milestone: --- with GCC 12, the following command fails with a fairly obscure error: $ gcc12.2.0 -c foo.h -o /dev/null foo.h:1: fatal error: cannot write PCH file: required memory segment unavailable compilation terminated. This also fails when invoked via g++. It works fine if the output is a normal file, and it always worked with previous GCC versions, so this is a pretty surprising change. This may seem like a strange thing to want to do, but I maintain a number of builds that do similar invocations to verify that each header file is self-contained. Either way, I think it would be best to fix it, or if that's not possible, it would be nice to improve the error message at the very least.
next reply other threads:[~2023-02-08 21:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 21:59 matt at immute dot net [this message] 2023-02-08 22:09 ` [Bug pch/108732] " pinskia at gcc dot gnu.org 2023-02-08 22:11 ` pinskia at gcc dot gnu.org 2023-02-08 22:23 ` matt at immute dot net 2023-02-08 22:45 ` pinskia at gcc dot gnu.org 2023-02-08 22:56 ` matt at immute dot net 2023-02-08 23:01 ` pinskia at gcc dot gnu.org 2023-02-08 23:15 ` matt at immute dot net 2023-05-22 23:16 ` justinpopo6 at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-108732-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).