public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "christophe.lyon at st dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59787] New: [ARM] mmx-2.c causes ICE when GCC is configured for cortex-a5/vfpv3-d16-fp16
Date: Mon, 13 Jan 2014 13:49:00 -0000	[thread overview]
Message-ID: <bug-59787-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 59787
           Summary: [ARM] mmx-2.c causes ICE when GCC is configured for
                    cortex-a5/vfpv3-d16-fp16
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: christophe.lyon at st dot com

I've noticed that gcc.target/arm/mmx-2 causes GCC to crash when GCC is
configured as:
--target=arm-none-linux-gnueabihf
--with-cpu=cortex-a5
--with-fpu=vfpv3-d16-fp16

testsuite/gcc.target/arm/mmx-2.c:166:1: internal compiler error: Max. number of
generated reload insns per insn is achieved (90)

0x9a5a32 lra_constraints(bool)
        /aci-gcc-fsf/sources/gcc-fsf/trunk/gcc/lra-constraints.c:4017
0x98e1f2 lra(_IO_FILE*)
        /aci-gcc-fsf/sources/gcc-fsf/trunk/gcc/lra.c:2339
0x9322b7 do_reload
        /aci-gcc-fsf/sources/gcc-fsf/trunk/gcc/ira.c:5455
0x932496 rest_of_handle_reload
        /aci-gcc-fsf/sources/gcc-fsf/trunk/gcc/ira.c:5584
0x9324ae execute
        /aci-gcc-fsf/sources/gcc-fsf/trunk/gcc/ira.c:5613


             reply	other threads:[~2014-01-13 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 13:49 christophe.lyon at st dot com [this message]
2014-01-14 13:51 ` [Bug target/59787] " renlin.li at arm dot com
2014-01-14 19:07 ` vmakarov at gcc dot gnu.org
2014-01-15 20:08 ` rearnsha at gcc dot gnu.org
2014-01-15 21:42 ` renlin.li at arm dot com
2014-01-15 21:51 ` rearnsha 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-59787-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).