public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/61977] powerpc preprocessor breaks on lines that end with "vector" Date: Tue, 31 Mar 2015 17:51:00 -0000 [thread overview] Message-ID: <bug-61977-4-2KBFdo9IEQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61977-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61977 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The problem is that cpp_peek_token, if it returns CPP_EOF, is fatal in the preprocessing: do { peektok = _cpp_lex_token (pfile); if (peektok->type == CPP_EOF) return peektok; } while (index--); but the macro_to_expand stuff (for which cpp_peek_token has been written, BTW) really assumes that it can non-destructively peek tokens when needed.
next prev parent reply other threads:[~2015-03-31 17:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-31 15:32 [Bug target/61977] New: powerpc-eabi " drivshin at allworx dot com 2015-03-20 19:18 ` [Bug target/61977] " drivshin at allworx dot com 2015-03-31 17:11 ` [Bug target/61977] powerpc " msebor at gcc dot gnu.org 2015-03-31 17:29 ` trippels at gcc dot gnu.org 2015-03-31 17:51 ` jakub at gcc dot gnu.org [this message] 2015-03-31 18:07 ` [Bug preprocessor/61977] [4.8/4.9/5 Regression] " jakub at gcc dot gnu.org 2015-03-31 18:26 ` jakub at gcc dot gnu.org 2015-04-01 14:57 ` jakub at gcc dot gnu.org 2015-04-02 11:55 ` jakub at gcc dot gnu.org 2015-04-02 12:08 ` jakub at gcc dot gnu.org 2015-04-06 17:02 ` jakub at gcc dot gnu.org 2015-04-06 17:04 ` jakub 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=bug-61977-4-2KBFdo9IEQ@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: 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).