public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sirl@gcc.gnu.org
To: blofeldus@yahoo.com, dje@watson.ibm.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, mark@codesourcery.com, nobody@gcc.gnu.org
Subject: Re: c/6543: Internal compiler error in extract_insn, at recog.c:2132
Date: Fri, 03 May 2002 06:53:00 -0000	[thread overview]
Message-ID: <20020503135336.27165.qmail@sources.redhat.com> (raw)

Synopsis: Internal compiler error in extract_insn, at recog.c:2132

State-Changed-From-To: feedback->analyzed
State-Changed-By: sirl
State-Changed-When: Fri May  3 06:53:36 2002
State-Changed-Why:
    PPC, reproduced on entropy, .i attached.
    
    Actually another incarnation of the CLOBBER problem, but harder to fix this time. This pattern around line 10730 in rs6000.md is the culprit:
    
    (define_insn ""
      [(set (match_operand:SI 0 "gpc_reg_operand" "=r,r,r,r,r")
            (eq:SI (match_operand:SI 1 "gpc_reg_operand" "%r,r,r,r,r")
                   (match_operand:SI 2 "reg_or_cint_operand" "r,O,K,L,I")))
       (clobber (match_scratch:SI 3 "=r,&r,r,r,r"))]
      "! TARGET_POWERPC64"
      "@
       xor %0,%1,%2\;{sfi|subfic} %3,%0,0\;{ae|adde} %0,%3,%0
       {sfi|subfic} %3,%1,0\;{ae|adde} %0,%3,%1
       {xoril|xori} %0,%1,%b2\;{sfi|subfic} %3,%0,0\;{ae|adde} %0,%3,%0
       {xoriu|xoris} %0,%1,%u2\;{sfi|subfic} %3,%0,0\;{ae|adde} %0,%3,%0
       {sfi|subfic} %0,%1,%2\;{sfi|subfic} %3,%0,0\;{ae|adde} %0,%3,%0"
      [(set_attr "length" "12,8,12,12,12")])
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6543


             reply	other threads:[~2002-05-03 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03  6:53 sirl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-04 16:14 dje
2002-05-03 10:38 dje
2002-05-03  5:20 jakub
2002-05-02 19:16 blofeldus

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=20020503135336.27165.qmail@sources.redhat.com \
    --to=sirl@gcc.gnu.org \
    --cc=blofeldus@yahoo.com \
    --cc=dje@watson.ibm.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=nobody@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).