public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "renlin.li at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63424] Octave -O3 build: internal compiler error: in prepare_cmp_insn, at optabs.c:4237
Date: Wed, 22 Oct 2014 08:58:00 -0000	[thread overview]
Message-ID: <bug-63424-4-rRNexKypLy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63424-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Renlin Li <renlin.li at arm dot com> ---
VEC_COND_EXPR with V2DI mode is generated as aarch64 target supports it
(vcond<mode><mode>). The VEC_COND_EXPR expression will further folded into
MIN_EXPR/MAX_EXPR expression in the dom pass.

However, aarch64 min/max expanders don't support V2DI mode. The compiler tries
to generate compare and jump sequence for this, and no vector compare can be
found(aarch64 dose have one, however, the compiler uses cbranch as a key to
search for a compare insn). And no library function is provided, it asserts.


  parent reply	other threads:[~2014-10-22  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  8:43 [Bug c++/63424] New: " david.sherwood at arm dot com
2014-10-21 14:08 ` [Bug target/63424] " renlin.li at arm dot com
2014-10-22  8:58 ` renlin.li at arm dot com [this message]
2014-10-28 10:11 ` renlin.li at arm dot com
2014-11-19 16:35 ` renlin at gcc dot gnu.org
2014-11-27 14:30 ` [Bug target/63424] [4.9 regression] " ramana at gcc dot gnu.org
2015-01-13 16:25 ` renlin at gcc dot gnu.org
2015-01-13 16:32 ` renlin 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-63424-4-rRNexKypLy@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).