public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/37215] ICE on 'gcc -E -dM -fpreprocessed - < /dev/null' Date: Fri, 02 Jan 2009 17:07:00 -0000 [thread overview] Message-ID: <20090102170500.966.qmail@sourceware.org> (raw) In-Reply-To: <bug-37215-16628@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from tromey at gcc dot gnu dot org 2009-01-02 17:04 ------- read_original_filename lexes a token, which hits EOF, which causes the buffer to be popped. This is sort of an odd scenario. Perhaps working around it in preprocess_file is best. -- tromey at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37215
next prev parent reply other threads:[~2009-01-02 17:07 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 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 [this message] 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 [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 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
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=20090102170500.966.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: 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).