public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "coyote at coyotegulch dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/15464] New: ICE: unable to find a register to spill in class `DREG'
Date: Sun, 16 May 2004 14:23:00 -0000	[thread overview]
Message-ID: <20040515153712.15464.coyote@coyotegulch.com> (raw)

When compiling the attached program with

gcc -c -std=gnu99 -O1 -march=pentium4 -fschedule-insns -funit-at-a-time
-fno-inline bug_reg_spill.c

GCC mainline (3.5.0 20040514) expresses an ICE:

bug_reg_spill.c: In function `decode':
bug_reg_spill.c:135: error: unable to find a register to spill in class `DREG'
bug_reg_spill.c:135: error: this is the insn:
(insn 52 51 53 14 (parallel [
            (set (reg:SI 0 ax [95])
                (udiv:SI (reg:SI 0 ax [93])
                    (reg/v:SI 4 si [orig:70 range ] [70])))
            (set (reg:SI 96)
                (umod:SI (reg:SI 0 ax [93])
                    (reg/v:SI 4 si [orig:70 range ] [70])))
            (clobber (reg:CC 17 flags))
        ]) 190 {udivmodsi4} (insn_list 51 (insn_list 42 (nil)))
    (expr_list:REG_DEAD (reg:SI 0 ax [93])
        (expr_list:REG_UNUSED (reg:CC 17 flags)
            (expr_list:REG_UNUSED (reg:SI 96)
                (nil)))))
bug_reg_spill.c:135: confused by earlier errors, bailing out


I believe this is different from bug 15318, but the causes might be similar. 

This ICE does not occur on my X86_64 system, or if the -march=pentium4 flag is
removed from the compile command.

-- 
           Summary: ICE: unable to find a register to spill in class `DREG'
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: coyote at coyotegulch dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-pc-linux
  GCC host triplet: i686-pc-linux
GCC target triplet: i686-pc-linux


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


             reply	other threads:[~2004-05-15 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 14:23 coyote at coyotegulch dot com [this message]
2004-05-16 14:26 ` [Bug c/15464] " coyote at coyotegulch dot com
2004-05-16 18:42 ` [Bug rtl-optimization/15464] " pinskia at gcc dot gnu dot org
2004-08-15  3:12 ` 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=20040515153712.15464.coyote@coyotegulch.com \
    --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).