public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/59569] New: [4.9 Regression] r206148 causes internal compiler error: in vect_create_destination_var, at tree-vect-data-refs.c:4294
Date: Sat, 21 Dec 2013 01:07:00 -0000	[thread overview]
Message-ID: <bug-59569-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59569

            Bug ID: 59569
           Summary: [4.9 Regression] r206148 causes internal compiler
                    error: in vect_create_destination_var, at
                    tree-vect-data-refs.c:4294
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com
                CC: bmei at broadcom dot com

When compiling 253.perlbmk from SPEC CPU 2K on Linux/x86-64,
I got

[hjl@gnu-mic-2 00000001]$
/export/project/git/gcc-regression/master/206150/usr/bin/gcc -c -o pp.o  
-DSPEC_CPU2000_LP64 -DSPEC_CPU2000_LINUX_I386 -DSPEC_CPU2000_NEED_BOOL
-DSPEC_CPU2000_GLIBC22        -O3 -funroll-loops -ffast-math   pp.c
In file included from perl.h:1090:0,
                 from pp.c:16:
handy.h:71:0: warning: "bool" redefined [enabled by default]
 #  define bool char
 ^
In file included from config.h:1:0,
                 from perl.h:137,
                 from pp.c:16:
spec_config.h:160:0: note: this is the location of the previous definition
 #define bool int
 ^
In file included from perl.h:2121:0,
                 from pp.c:16:
pp.c: In function \u2018Perl_pp_splice\u2019:
embed.h:759:20: internal compiler error: in vect_create_destination_var, at
tree-vect-data-refs.c:4294
 #define pp_splice  Perl_pp_splice
                    ^
pp.h:20:20: note: in definition of macro \u2018PP\u2019
 #define PP(s) OP * s(ARGSproto)
                    ^
pp.c:2687:4: note: in expansion of macro \u2018pp_splice\u2019
 PP(pp_splice)
    ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
[hjl@gnu-mic-2 00000001]$


             reply	other threads:[~2013-12-21  1:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21  1:07 hjl.tools at gmail dot com [this message]
2013-12-21  1:12 ` [Bug middle-end/59569] " hjl.tools at gmail dot com
2013-12-21  1:48 ` hjl.tools at gmail dot com
2013-12-21 10:10 ` jakub at gcc dot gnu.org
2013-12-21 19:20 ` su at cs dot ucdavis.edu
2013-12-22 18:11 ` dcb314 at hotmail dot com
2013-12-22 21:42 ` hjl.tools at gmail dot com
2013-12-23  7:21 ` dcb314 at hotmail dot com
2013-12-23  8:46 ` jakub at gcc dot gnu.org
2013-12-23 10:25 ` bmei at broadcom dot com
2013-12-23 10:57 ` bmei at broadcom dot com
2013-12-23 11:51 ` jakub at gcc dot gnu.org
2013-12-23 15:08 ` meibf at gcc dot gnu.org
2014-01-02 14:10 ` 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-59569-4@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).