public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/40934] [4.5 Regression] ICE in get_hard_regnum, at reg-stack.c:741
Date: Sat, 01 Aug 2009 22:39:00 -0000	[thread overview]
Message-ID: <20090801223850.18081.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40934-17247@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from ubizjak at gmail dot com  2009-08-01 22:38 -------
(In reply to comment #5)

> (jump_insn:TI 52 50 56 11 test.c:32 (parallel [
>             (set (pc)
>                 (if_then_else (le (reg/v:SF 9 st(1) [orig:64 move ] [64])
>                         (reg:SF 8 st [80]))
>                     (label_ref:SI 60)
>                     (pc)))
>             (clobber (reg:CCFP 18 fpsr))
>             (clobber (reg:CCFP 17 flags))
>             (clobber (reg:HI 0 ax))
>         ]) 626 {*fp_jcc_3_387} (expr_list:REG_DEAD (reg/v:SF 9 st(1) [orig:64
> move ] [64])

This instruction should be split waaay before reg-stack. The problem was
probably introduced by the patch below:

2009-06-28  Paolo Bonzini  <bonzini@gnu.org>

        * config/i386/i386.h (enum ix86_fpcmp_strategy): New.
        * config/i386/i386.md (cbranchxf4, cstorexf4, cbranch<MODEF>4,
        cstore<MODEF>4, mov<X87MODEF>cc): Change predicate to
        ix86_fp_comparison_operator.
        (*fp_jcc_1_mixed, *fp_jcc_1_sse, *fp_jcc_1_387, *fp_jcc_2_mixed,
        *fp_jcc_2_sse, *fp_jcc_2_387): Delete
        (*fp_jcc_3_387, *fp_jcc_4_387, *fp_jcc_5_387, *fp_jcc_6_387,
        *fp_jcc_7_387, *fp_jcc_8<MODEF>_387): Eliminate call to
        !ix86_use_fcomi_compare, change ix86_fp_jump_nontrivial_p call
        to !TARGET_CMOVE, change predicate to ix86_fp_comparison_operator.
        (related splits): Change predicate to ix86_fp_comparison_operator.
        * config/i386/predicates.md: Use ix86_trivial_fp_comparison_operator
        instead of ix86_fp_comparison_codes.
        ...

Let's ask Paolo.


-- 

ubizjak at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bonzini at gnu dot org


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


  parent reply	other threads:[~2009-08-01 22:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01 20:06 [Bug c/40934] New: " sezeroz at gmail dot com
2009-08-01 20:11 ` [Bug c/40934] " sezeroz at gmail dot com
2009-08-01 20:12 ` sezeroz at gmail dot com
2009-08-01 20:26 ` [Bug target/40934] " sezeroz at gmail dot com
2009-08-01 22:04 ` [Bug target/40934] [4.5 Regression] " ubizjak at gmail dot com
2009-08-01 22:25 ` ubizjak at gmail dot com
2009-08-01 22:39 ` ubizjak at gmail dot com [this message]
2009-08-01 22:58 ` bonzini at gnu dot org
2009-08-01 23:11 ` sezeroz at gmail dot com
2009-08-01 23:41 ` bonzini at gnu dot org
2009-08-01 23:59 ` bonzini at gnu dot org
2009-08-02  0:15 ` bonzini at gnu dot org
2009-08-02  9:32 ` sezeroz at gmail dot com
2009-08-02 10:00 ` ubizjak at gmail dot com
2009-08-12 18:20 ` sezeroz at gmail dot com
2009-08-14 12:14 ` bonzini at gcc dot gnu dot org
2009-08-14 12:17 ` bonzini at gnu dot org
2009-08-14 12:29 ` sezeroz at gmail dot com
2009-08-16 20:25 ` hjl 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=20090801223850.18081.qmail@sourceware.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).