public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patriciak784-gccmainling at yahoo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/37215] ICE on 'gcc -E -dM -fpreprocessed - < /dev/null'
Date: Sun, 15 Jan 2012 14:55:00 -0000 [thread overview]
Message-ID: <bug-37215-4-GSmL7gU8W8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-37215-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37215
--- Comment #13 from patriciak784-gccmainling at yahoo dot de 2012-01-15 14:27:00 UTC ---
(In reply to comment #12)
> On inspecting this more closely, I agree with patriciak784. The issue isn't
> directly related to the fix of Richard for PR20239.
>
> So I suggest patch for c-family/c-ppoutput.c as following:
>
> Index: c-family/c-ppoutput.c
> ===================================================================
> --- c-family/c-ppoutput.c (revision 183106)
> +++ c-family/c-ppoutput.c (working copy)
> @@ -86,7 +86,7 @@
> {
> /* A successful cpp_read_main_file guarantees that we can call
> cpp_scan_nooutput or cpp_get_token next. */
> - if (flag_no_output)
> + if (flag_no_output && pfile->buffer)
> {
> /* Scan -included buffers, then the main file. */
> while (pfile->buffer->prev)
I'd welcome if this patch was included in GCC.
next prev parent reply other threads:[~2012-01-15 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-37215-4@http.gcc.gnu.org/bugzilla/>
2012-01-13 23:10 ` ktietz at gcc dot gnu.org
2012-01-15 14:55 ` patriciak784-gccmainling at yahoo dot de [this message]
2012-06-27 14:04 ` ktietz at gcc dot gnu.org
2012-06-27 15:07 ` ktietz at gcc dot gnu.org
2012-06-27 15:11 ` ktietz at gcc dot gnu.org
2008-08-23 22:01 [Bug preprocessor/37215] New: " gcc-bugzilla at gcc dot gnu dot org
2008-08-24 22:13 ` [Bug preprocessor/37215] " pinskia at gcc dot gnu dot org
2008-09-03 21:16 ` pinskia at gcc dot gnu dot org
2008-09-04 13:36 ` patriciak784-gccmainling at yahoo dot de
2008-09-04 16:39 ` patriciak784-gccmainling at yahoo dot de
2008-09-07 14:42 ` patriciak784-gccmainling at yahoo dot de
2009-01-02 17:07 ` tromey at gcc dot gnu dot org
2009-01-04 20:26 ` patriciak784-gccmainling at yahoo dot de
2009-01-04 20:53 ` patriciak784-gccmainling at yahoo dot de
2009-01-05 8:43 ` patriciak784-gccmainling at yahoo dot de
2009-02-01 11:23 ` patriciak784-gccmainling at yahoo dot de
2009-02-01 11:45 ` patriciak784-gccmainling at yahoo dot de
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-37215-4-GSmL7gU8W8@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: 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).