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 pch/108732] Pre-compiled headers cannot be output to /dev/null Date: Wed, 08 Feb 2023 22:23:20 +0000 [thread overview] Message-ID: <bug-108732-4-avPtSX1kD8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108732-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108732 --- Comment #3 from Matt Hellige <matt at immute dot net> --- 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 case?) 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 user suspect that /dev/null can be used for both input and output of that gcc -xc invocation, but not the other one?
next prev parent reply other threads:[~2023-02-08 22:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 21:59 [Bug c/108732] New: " matt at immute dot net 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 [this message] 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-avPtSX1kD8@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).