public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/20285] New: [3.3/3.4/4.0/4.1 Regression] gcc -E - < . gives a misleading error message Date: Wed, 02 Mar 2005 16:23:00 -0000 [thread overview] Message-ID: <20050302162258.20285.pinskia@gcc.gnu.org> (raw) With the mainline I get: cc1: error: stdout: No such file or directory With 2.95.3, I got: cpp0: Input file `' is a directory -- Summary: [3.3/3.4/4.0/4.1 Regression] gcc -E - < . gives a misleading error message Product: gcc Version: 4.0.0 Status: UNCONFIRMED Keywords: diagnostic Severity: minor Priority: P2 Component: preprocessor AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20285
next reply other threads:[~2005-03-02 16:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-02 16:23 pinskia at gcc dot gnu dot org [this message] 2005-03-02 16:24 ` [Bug preprocessor/20285] " pinskia at gcc dot gnu dot org 2005-03-17 17:49 ` pinskia at gcc dot gnu dot org 2005-04-21 5:05 ` mmitchel at gcc dot gnu dot org 2005-07-01 22:15 ` [Bug preprocessor/20285] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org 2005-09-27 16:15 ` mmitchel at gcc dot gnu dot 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=20050302162258.20285.pinskia@gcc.gnu.org \ --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).