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 preprocessor/61977] [4.8/4.9/5 Regression] powerpc preprocessor breaks on lines that end with "vector"
Date: Thu, 02 Apr 2015 11:55:00 -0000	[thread overview]
Message-ID: <bug-61977-4-Ks23ggP5qF@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

--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Apr  2 11:54:58 2015
New Revision: 221838

URL: https://gcc.gnu.org/viewcvs?rev=221838&root=gcc&view=rev
Log:
    PR preprocessor/61977
    * config/rs6000/rs6000-c.c (rs6000_cpu_cpp_builtins): Don't
    predefine __vector/__bool/__pixel macros nor context sensitive
    macros for CLK_ASM.
    * config/spu/spu-c.c (spu_cpu_cpp_builtins): Similarly.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/config/rs6000/rs6000-c.c
    trunk/gcc/config/spu/spu-c.c


  parent reply	other threads:[~2015-04-02 11:55 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
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 [this message]
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-Ks23ggP5qF@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).