public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/47547] New: WHOPR, can't use /dev/null as an output file Date: Mon, 31 Jan 2011 05:13:00 -0000 [thread overview] Message-ID: <bug-47547-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47547 Summary: WHOPR, can't use /dev/null as an output file Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: trivial Priority: P3 Component: driver AssignedTo: unassigned@gcc.gnu.org ReportedBy: d.g.gorbachev@gmail.com $ touch empty.c $ gcc -flto empty.c -o /dev/null lto1: fatal error: can't open /dev/null.s for writing: Permission denied [...]
next reply other threads:[~2011-01-30 23:41 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-31 5:13 d.g.gorbachev at gmail dot com [this message] 2011-01-31 14:27 ` [Bug driver/47547] " rguenth at gcc dot gnu.org 2011-01-31 15:06 ` hjl.tools at gmail dot com 2011-01-31 17:35 ` hjl.tools at gmail dot com 2011-01-31 17:41 ` hjl.tools at gmail dot com 2011-01-31 20:08 ` [Bug driver/47547] [4.5/4.6 Regression] " hjl.tools at gmail dot com 2011-02-01 14:42 ` hjl at gcc dot gnu.org 2011-02-01 14:43 ` [Bug driver/47547] [4.5 " hjl.tools at gmail dot com 2011-02-02 18:27 ` dnovillo at gcc dot gnu.org 2011-03-08 13:27 ` rguenth at gcc dot gnu.org 2011-04-10 10:16 ` rguenth at gcc dot gnu.org
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-47547-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).