public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/53487] New: [4.8 Regression] Unrecognizable insn for conditional move
Date: Fri, 25 May 2012 16:02:00 -0000	[thread overview]
Message-ID: <bug-53487-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53487
           Summary: [4.8 Regression] Unrecognizable insn for conditional
                    move
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: wschmidt@gcc.gnu.org
                CC: bergner@gcc.gnu.org, meissner@gcc.gnu.org,
                    pinskia@gcc.gnu.org
              Host: powerpc64-linux
            Target: powerpc64-linux
             Build: powerpc64-linux


Created attachment 27496
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27496
Reduced testcase

The attached test (reduced from 456.hmmer) fails to compile beginning with
r187183, as shown:

wschmidt@bns:~/delta> gcc -c -o cluster.o  -m64 -O3 -mcpu=power7 -ffast-math
-misel cluster.i
cluster.i: In function ‘Cluster’:
cluster.i:30:1: error: unrecognizable insn:
 }
 ^
(insn 156 155 157 8 (set (reg:SI 289)
        (if_then_else:SI (ge (reg:SF 291)
                (const_double:SF 0.0 [0x0.0p+0]))
            (subreg/s:SI (reg/v:DI 258 [ i+-4 ]) 4)
            (subreg/s:SI (reg/v:DI 265 [ row+-4 ]) 4))) -1
     (nil))
cluster.i:30:1: internal compiler error: in extract_insn, at recog.c:2130
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

This form of conditional move insn isn't recognized on powerpc64 because the
floating-point comparison is incompatible with a conditional move of integer
arguments.  Prior to this revision, code generation recognized the
incompatibility and did not generate the conditional move.

r187183 is:

2012-05-04  Andrew Pinski  <apinski@cavium.com>

    * expr.c (get_def_for_expr_class): New function.
    (convert_tree_comp_to_rtx): New function.
    (expand_cond_expr_using_cmove): New function.
    (expand_expr_real_2 <case COND_EXPR>): Call
    expand_cond_expr_using_cmove first and return if it succeeds.
    Remove the check for HAVE_conditional_move since we should have
    already converted it to a conditional move.
    * config/i386/i386.c (ix86_expand_int_movcc): Disallow comparison
    modes of DImode for 32bits and TImode.


             reply	other threads:[~2012-05-25 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 16:02 wschmidt at gcc dot gnu.org [this message]
2012-05-25 16:04 ` [Bug rtl-optimization/53487] " wschmidt at gcc dot gnu.org
2012-05-25 16:13 ` wschmidt at gcc dot gnu.org
2012-05-25 16:16 ` wschmidt at gcc dot gnu.org
2012-05-25 17:54 ` [Bug target/53487] " pinskia at gcc dot gnu.org
2012-06-05 19:41 ` meissner at gcc dot gnu.org
2012-08-16 23:00 ` meissner 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-53487-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).