public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drivshin at allworx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61977] powerpc-eabi preprocessor breaks on lines that end with "vector"
Date: Fri, 20 Mar 2015 19:18:00 -0000	[thread overview]
Message-ID: <bug-61977-4-OJxKDMw7of@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

David Rivshin <drivshin at allworx dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|                            |powerpc-eabi
      Known to work|                            |4.9.0
      Known to fail|                            |4.9.1, 4.9.2

--- Comment #1 from David Rivshin <drivshin at allworx dot com> ---
This is still happening in the latest trunk and latest 4.9 branch code.

Simplified steps to reproduce:
../gcc.svn/configure --prefix=${PWD}/../local --enable-languages=c
--with-gnu-as --with-gnu-ld --disable-libstdcxx-pch --target=powerpc-eabi
--disable-shared --with-newlib
make all-gcc
make install-gcc
echo -e "# comment ending in vector" | ../local/bin/powerpc-eabi-cpp -x
assembler-with-cpp


I'm fairly certain this is the same root cause as bug 51654, and changeset
r210055 just exposed some non-altivec powerpc targets to it. In addition to the
workarounds mentioned there (bug 51654, comment 3), removing the call to
init_vector_keywords() in rs6000_cpu_cpp_builtins() also works. 

Since those vector keywords only have effect if TARGET_ALTIVEC (see
rs6000_macro_to_expand()), making their definition conditional upon
TARGET_ALTIVEC resolves the 4.9.1 regression (as best I can tell). Although
that obviously does not resolve the underlying issue, which has existed since
at least 4.6 (according to bug 51654).


  reply	other threads:[~2015-03-20 18:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 15:32 [Bug target/61977] New: " drivshin at allworx dot com
2015-03-20 19:18 ` drivshin at allworx dot com [this message]
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
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-OJxKDMw7of@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).