public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/17984] New: Recent peephole2:s may cause internal compiler errors (2)
Date: Wed, 13 Oct 2004 23:14:00 -0000	[thread overview]
Message-ID: <20041013231425.17984.hp@gcc.gnu.org> (raw)

See also PR 17626.  This is another bug in the peephole2 patterns; constants
aren't truncated/sign-extended when changing to a shorter mode.  This causes
ICEs like the following:
x/gcc/testsuite/gcc.dg/cris-peep2-xsrand2.c: In function 'andwlsr':
x/gcc/testsuite/gcc.dg/cris-peep2-xsrand2.c:16: error: unrecognizable insn:
(insn 31 30 25 0 (set (reg:HI 10 r10)
        (and:HI (reg:HI 10 r10)
            (const_int 65399 [0xff77]))) -1 (nil)
    (nil))
x/gcc/testsuite/gcc.dg/cris-peep2-xsrand2.c:16: internal compiler error: in
extract_insn, at recog.c:2034

-- 
           Summary: Recent peephole2:s may cause internal compiler errors
                    (2)
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: hp at gcc dot gnu dot org
        ReportedBy: hp at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: cris-*


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


             reply	other threads:[~2004-10-13 23:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 23:14 hp at gcc dot gnu dot org [this message]
2004-10-13 23:32 ` [Bug target/17984] " cvs-commit at gcc dot gnu dot org
2004-10-13 23:35 ` cvs-commit at gcc dot gnu dot org
2004-10-13 23:38 ` hp at gcc dot gnu dot org
2004-10-15 17:13 ` pinskia at gcc dot gnu dot 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=20041013231425.17984.hp@gcc.gnu.org \
    --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).