public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "chappich at techfak dot uni-bielefeld dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/17610] New: Empty #include statement halts gcc Date: Wed, 22 Sep 2004 14:32:00 -0000 [thread overview] Message-ID: <20040922143248.17610.chappich@techfak.uni-bielefeld.de> (raw) The gcc binary halts if the source code contains an empty '#include' statement. Prior versions, e.g. 3.3.1, used to print "empty file name in #include". This can be easily reproduced with a one-line source file containing nothing more than '#include ""'. -- Summary: Empty #include statement halts gcc Product: gcc Version: 3.4.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: chappich at techfak dot uni-bielefeld dot de CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17610
next reply other threads:[~2004-09-22 14:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-22 14:32 chappich at techfak dot uni-bielefeld dot de [this message] 2004-09-22 18:14 ` [Bug preprocessor/17610] " pinskia at gcc dot gnu dot org 2004-09-22 21:18 ` [Bug preprocessor/17610] [3.4/4.0 Regression] " pinskia at gcc dot gnu dot org 2004-09-22 21:56 ` Neil Booth 2004-09-22 21:56 ` neil at daikokuya dot co dot uk 2004-11-01 0:47 ` mmitchel at gcc dot gnu dot org 2004-11-27 20:30 ` neroden at gcc dot gnu dot org 2004-11-27 22:50 ` neroden at gcc dot gnu dot org 2004-11-28 22:28 ` cvs-commit at gcc dot gnu dot org 2004-12-02 2:33 ` [Bug preprocessor/17610] [3.4 " cvs-commit at gcc dot gnu dot org 2004-12-02 2:37 ` neroden 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=20040922143248.17610.chappich@techfak.uni-bielefeld.de \ --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).