public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "justinpopo6 at gmail dot com" <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: Mon, 22 May 2023 23:16:05 +0000 [thread overview] Message-ID: <bug-108732-4-oDKvUBaNZ6@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 Justin Chen <justinpopo6 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |justinpopo6 at gmail dot com --- Comment #8 from Justin Chen <justinpopo6 at gmail dot com> --- I ran into the exact issue. Took me a while to figure out the issue was "-o /dev/null". The inconsistency also caught me off guard. I agree we need some consistency here.
prev parent reply other threads:[~2023-05-22 23:16 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 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 [this message]
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-oDKvUBaNZ6@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).