public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: sje@cup.hp.com
Cc: gcc@gcc.gnu.org
Subject: Re: IA64 floating point division question
Date: Tue, 31 Aug 2004 23:58:00 -0000	[thread overview]
Message-ID: <87656y3m8i.fsf@codesourcery.com> (raw)
In-Reply-To: <200408312246.PAA26407@hpsje.cup.hp.com> (Steve Ellcey's message of "Tue, 31 Aug 2004 15:46:47 -0700 (PDT)")

Steve Ellcey <sje@cup.hp.com> writes:

> y.c: In function `foo':
> y.c:9: error: unrecognizable insn:
> (insn 36 19 37 0 (parallel [
>             (set (reg:SF 351)
>                 (div:SF (const_int 1 [0x1])
>                     (reg:SF 350 [ b ])))
>             (set (scratch:BI)
>                 (unspec:BI [
>                         (reg:SF 349 [ a ])
>                         (reg:SF 350 [ b ])
>                     ] 14))
>             (use (const_int 1 [0x1]))
>         ]) -1 (nil)
>     (expr_list:REG_UNUSED (scratch:BI)
>         (expr_list:REG_UNUSED (scratch:BI)
>             (nil))))
> y.c:9: internal compiler error: in extract_insn, at recog.c:2037

I'm fairly sure that your problem is with the "*recip_approx"
instruction, which is what is supposed to match this pattern.  The
catch is, it *only* allows XFmode operands, whereas you're trying to
feed it SFmode.

I'm not sure how to fix this.  When I tried to do something similar, I
got completely stuck because I couldn't make GCC refer to the *same*
pseudo register in two different modes.

zw

  reply	other threads:[~2004-08-31 23:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31 23:20 Steve Ellcey
2004-08-31 23:58 ` Zack Weinberg [this message]
2004-09-01 12:25   ` Joern Rennecke
2004-09-01 12:28 ` Joern Rennecke
2004-09-01 17:51   ` Steve Ellcey
     [not found] <200408312358.QAA26610@hpsje.cup.hp.com>
2004-09-01  0:10 ` Zack Weinberg

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=87656y3m8i.fsf@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=sje@cup.hp.com \
    /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).