public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stemidts at cisco dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52855] ARM: Internal compiler error: in extract_insn, at recog.c:2109
Date: Fri, 16 Nov 2012 09:48:00 -0000	[thread overview]
Message-ID: <bug-52855-4-5svuLsR44T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52855-4@http.gcc.gnu.org/bugzilla/>


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

Steinar Midtskogen <stemidts at cisco dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stemidts at cisco dot com

--- Comment #4 from Steinar Midtskogen <stemidts at cisco dot com> 2012-11-16 09:48:36 UTC ---
I've run into the same bug.  The code below reproduces it:

#include <arm_neon.h>

static const __attribute__((aligned(16)))
int16_t c[][2][8] =
{
    { { 0 }, { 0 } }, { { 0 }, { 0 } }, { { 0 }, { 0 } }, { { 0 }, { 0 } },
    { { 0 }, { 0 } }, { { 0 }, { 0 } }, { { 0 }, { 0 } }, { { 0 }, { 0 } }
};


int16x8_t test2(int off)
{
    return vld1q_u8((uint8_t*)c[off][0]);
}

int16x8_t test(int off, uint8_t **c)
{
    static int8_t m[] = { 1, 2, 3 };
    long long cf = m[off];

    return vld1q_u8((uint8_t*)c[cf]);
}

Version: 4.6.3
Options: -mapcs-frame -mfloat-abi=softfp -mfpu=neon -flax-vector-conversions
-O1

Changing "long long cf" into "int cf" eliminates the crash.


  parent reply	other threads:[~2012-11-16  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 20:09 [Bug c/52855] New: " mpthompson at gmail dot com
2012-04-04 15:30 ` [Bug c/52855] " mpthompson at gmail dot com
2012-04-04 15:34 ` [Bug target/52855] " pinskia at gcc dot gnu.org
2012-10-24 13:38 ` mans at mansr dot com
2012-10-27 13:27 ` mikpe at it dot uu.se
2012-11-16  9:48 ` stemidts at cisco dot com [this message]
2012-11-28  3:22 ` ramana at gcc dot gnu.org
2014-02-16 13:17 ` jackie.rosen at hushmail 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-52855-4-5svuLsR44T@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).