public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neil at daikokuya dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/17610] [3.4/4.0 Regression] Empty #include statement halts gcc
Date: Wed, 22 Sep 2004 21:56:00 -0000 [thread overview]
Message-ID: <20040922215641.13129.qmail@sourceware.org> (raw)
In-Reply-To: <20040922143248.17610.chappich@techfak.uni-bielefeld.de>
------- Additional Comments From neil at daikokuya dot co dot uk 2004-09-22 21:56 -------
Subject: Re: [3.4/4.0 Regression] Empty #include statement halts gcc
pinskia at gcc dot gnu dot org wrote:-
>
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-09-22 21:18 -------
> Confirmed, but I really would like a preprocessor person to say if this is expected behavior.
Nope, it should be rejected outright like prior versions of GCC did.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17610
next prev parent reply other threads:[~2004-09-22 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 14:32 [Bug c/17610] New: " chappich at techfak dot uni-bielefeld dot de
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 [this message]
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=20040922215641.13129.qmail@sourceware.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: link
Be 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).