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/47744] [x32] ICE: in reload_cse_simplify_operands, at postreload.c:403
Date: Sun, 17 Jul 2011 20:08:00 -0000	[thread overview]
Message-ID: <bug-47744-4-evVRX109s8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47744-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Uros Bizjak <ubizjak at gmail dot com> 2011-07-17 20:07:38 UTC ---
(In reply to comment #13)
> Looking at the example in Comment #0, RTX expansion pass generates:
> 
> ;; D.2794_77 = &q + D.2793_76;
> 
> (insn 84 83 85 (parallel [
>             (set (reg:DI 173)
>                 (plus:DI (reg/f:DI 54 virtual-stack-vars)
>                     (const_int -160 [0xffffffffffffff60])))
>             (clobber (reg:CC 17 flags))
>         ]) pr47744.c:5 -1
>      (nil))
> 
> Why 64bit virtual register to hold &q _address_?

Later, reg:DI 173 gets propagated into (insn 89):

(insn 89 87 90 3 (set (reg:SI 177)
        (plus:SI (plus:SI (mult:SI (reg:SI 175)
                    (const_int 8 [0x8]))
                (subreg:SI (reg/f:DI 20 frame) 0))
            (const_int -160 [0xffffffffffffff60]))) pr47744.c:5 250
{*lea_2_x32}
     (expr_list:REG_DEAD (reg:SI 175)
        (nil)))

which chokes reload when trying to eliminate frame pointer:

(insn 89 87 90 3 (set (reg:SI 39 r10 [177])
        (plus:SI (plus:SI (mult:SI (reg:SI 0 ax [175])
                    (const_int 8 [0x8]))
                (subreg:SI (plus:DI (reg/f:DI 7 sp)
                        (const_int 200 [0xc8])) 0))
            (const_int -160 [0xffffffffffffff60]))) pr47744.c:5 250
{*lea_2_x32}
     (nil))


  parent reply	other threads:[~2011-07-17 20:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15  6:10 [Bug target/47744] New: " hjl.tools at gmail dot com
2011-02-15  6:30 ` [Bug target/47744] " hjl.tools at gmail dot com
2011-02-15 13:44 ` hjl at gcc dot gnu.org
2011-02-18 15:02 ` hjl.tools at gmail dot com
2011-02-18 19:38 ` hjl at gcc dot gnu.org
2011-03-01 17:27 ` hjl.tools at gmail dot com
2011-03-01 19:21 ` hjl at gcc dot gnu.org
2011-03-29  6:27 ` hjl.tools at gmail dot com
2011-04-02  5:31 ` hjl at gcc dot gnu.org
2011-04-02  5:50 ` hjl at gcc dot gnu.org
2011-07-17 17:26 ` ubizjak at gmail dot com
2011-07-17 17:27 ` ubizjak at gmail dot com
2011-07-17 18:29 ` hjl.tools at gmail dot com
2011-07-17 20:02 ` ubizjak at gmail dot com
2011-07-17 20:08 ` ubizjak at gmail dot com [this message]
2011-07-17 20:27 ` hjl.tools at gmail dot com
2011-07-17 21:14 ` ubizjak at gmail dot com
2011-07-17 21:21 ` hjl.tools at gmail dot com
2011-07-17 21:28 ` hjl.tools at gmail dot com
2011-07-17 22:04 ` ubizjak at gmail dot com
2011-07-17 22:12 ` hjl.tools at gmail dot com
2011-07-17 22:18 ` ubizjak at gmail dot com
2011-07-17 22:44 ` hjl.tools at gmail dot com
2011-07-17 22:48 ` ubizjak at gmail dot com
2011-07-17 22:55 ` hjl.tools at gmail dot com
2011-07-17 23:00 ` ubizjak at gmail dot com
2011-07-18  0:03 ` hjl.tools at gmail dot com
2011-07-18  4:18 ` hjl.tools at gmail dot com
2011-07-18  9:09 ` ubizjak at gmail dot com
2011-07-18 13:55 ` hjl.tools at gmail dot com
2011-07-18 14:01 ` ubizjak at gmail dot com
2011-07-18 14:04 ` hjl.tools at gmail dot com
2011-07-18 14:54 ` hjl.tools at gmail dot com
2011-07-18 16:54 ` ubizjak at gmail dot com
2011-07-18 16:56 ` hjl.tools at gmail dot com
2011-07-18 17:18 ` ubizjak at gmail dot com
2011-07-18 17:51 ` hjl at gcc dot gnu.org
2011-07-18 17:52 ` uros at gcc dot gnu.org
2011-07-18 17:54 ` hjl at gcc dot gnu.org
2011-07-18 18:30 ` ubizjak at gmail dot com
2011-08-03 14:08 ` hjl at gcc dot gnu.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=bug-47744-4-evVRX109s8@http.gcc.gnu.org/bugzilla/ \
    --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).