public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.abdurachmanov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64413] New: [AArch64/ARMv7] ICE in copy_to_mode_reg, at explow.c:654
Date: Fri, 26 Dec 2014 17:20:00 -0000	[thread overview]
Message-ID: <bug-64413-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64413

            Bug ID: 64413
           Summary: [AArch64/ARMv7] ICE in copy_to_mode_reg, at
                    explow.c:654
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: david.abdurachmanov at gmail dot com

Created attachment 34338
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34338&action=edit
testcase (AArch64, Fortran)

OpenLoops 1.0.1 package is failing to compile on AArch64 with GCC 4.9.{1,2}
there gfortran ICE'd:

test.f90: In function 'vert_aq_s':
test.f90:38:0: internal compiler error: in copy_to_mode_reg, at explow.c:654
     Jout_S%j(1) = 0
 ^

I managed to extract a minimal testcase (testcase.f90). It should be compiled
like this:

gfortran -o testcase.os -c -ffixed-line-length-0 -ffree-line-length-0 -O0 -O0
-fPIC testcase.f90

A similar ICE was recently posted (Oct 20) with GCC 4.9.1, ARMv7, C++ on
stackoverflow:
http://stackoverflow.com/questions/26474507/compiler-crash-with-arm-neon-datatypes

I.e., the ICE point to the same "copy_to_mode_reg, at explow.c:654". Might be
related.

Have not tested with GCC 5.0 (trunk).


             reply	other threads:[~2014-12-26 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 17:20 david.abdurachmanov at gmail dot com [this message]
2014-12-28 20:49 ` [Bug middle-end/64413] " david.abdurachmanov at gmail dot com

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-64413-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).