public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/49422] New: [arm] unable to find a register to spill in class 'VFP_LO_REGS'
@ 2011-06-15 13:32 philb at gnu dot org
  2011-06-20 18:58 ` [Bug target/49422] " mikpe at it dot uu.se
  2011-06-22 13:47 ` philb at gnu dot org
  0 siblings, 2 replies; 3+ messages in thread
From: philb at gnu dot org @ 2011-06-15 13:32 UTC (permalink / raw)
  To: gcc-bugs

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

           Summary: [arm] unable to find a register to spill in class
                    'VFP_LO_REGS'
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: philb@gnu.org
            Target: arm-linux


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

$ arm-oe-linux-gnueabi-gcc -fPIC -mfpu=vfp -O2 s_span.i -march=armv6j
-mtune=arm1136jf-s -mfloat-abi=softfp -ffast-math -S
swrast/s_span.c: In function '_swrast_write_rgba_span':
swrast/s_span.c:1297:1: error: unable to find a register to spill in class
'VFP_LO_REGS'
swrast/s_span.c:1297:1: error: this is the insn:
(insn 2389 2380 3422 269 (set (subreg:SI (reg:QI 2169) 0)
        (unsigned_fix:SI (fix:SF (reg/v:SF 78 s15 [orig:685 a ] [685]))))
swrast/s_span.c:867 670 {fixuns_truncsfsi2}
     (expr_list:REG_DEAD (reg/v:SF 78 s15 [orig:685 a ] [685])
        (nil)))
swrast/s_span.c:1297: confused by earlier errors, bailing out
$


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/49422] [arm] unable to find a register to spill in class 'VFP_LO_REGS'
  2011-06-15 13:32 [Bug target/49422] New: [arm] unable to find a register to spill in class 'VFP_LO_REGS' philb at gnu dot org
@ 2011-06-20 18:58 ` mikpe at it dot uu.se
  2011-06-22 13:47 ` philb at gnu dot org
  1 sibling, 0 replies; 3+ messages in thread
From: mikpe at it dot uu.se @ 2011-06-20 18:58 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Mikael Pettersson <mikpe at it dot uu.se> 2011-06-20 18:58:00 UTC ---
I've not been able to reproduce this ICE.  How exactly was your gcc configured
(arm-oe-linux-gnueabi-gcc -v)?


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug target/49422] [arm] unable to find a register to spill in class 'VFP_LO_REGS'
  2011-06-15 13:32 [Bug target/49422] New: [arm] unable to find a register to spill in class 'VFP_LO_REGS' philb at gnu dot org
  2011-06-20 18:58 ` [Bug target/49422] " mikpe at it dot uu.se
@ 2011-06-22 13:47 ` philb at gnu dot org
  1 sibling, 0 replies; 3+ messages in thread
From: philb at gnu dot org @ 2011-06-22 13:47 UTC (permalink / raw)
  To: gcc-bugs

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

philb at gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from philb at gnu dot org 2011-06-22 13:46:51 UTC ---
I can't reproduce it now either.  I think I must have been testing against a
locally patched tree rather than the clean one by mistake.  I'll close this bug
until/unless I can reproduce the failure on a released version.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-06-22 13:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-06-15 13:32 [Bug target/49422] New: [arm] unable to find a register to spill in class 'VFP_LO_REGS' philb at gnu dot org
2011-06-20 18:58 ` [Bug target/49422] " mikpe at it dot uu.se
2011-06-22 13:47 ` philb at gnu dot org

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).