public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/61572] [4.10 Regression] ICE: in assign_by_spills, at lra-assigns.c:1335
Date: Mon, 23 Jun 2014 19:50:00 -0000	[thread overview]
Message-ID: <bug-61572-4-fk8WVLkx2N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61572-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61572

--- Comment #3 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
When LRA processes insn 17 in BB3 it creates a reload pseudo 101 of DREG class

         Choosing alt 0 in insn 17:  (0) =d  (1) %a  (2) rm  (3) =1
{*smulsi3_highpart_1}
      Creating newreg=101 from oldreg=93, assigning class DREG to r101
      Creating newreg=102 from oldreg=100, assigning class AREG to r102
   17: {r101:SI=trunc(sign_extend(r102:SI)*sign_extend(r94:SI) 0>>0x20);clobber
r102:SI;clobber flags:CC;}
      REG_UNUSED r100:SI
      REG_DEAD r94:SI
      REG_UNUSED flags:CC
      REG_EQUAL trunc(sign_extend(r92:SI)*0x10624dd3 0>>0x20)
    Inserting insn reload before:
   63: r102:SI=r92:SI
    Inserting insn reload after:
   62: r93:SI=r101:SI

but LRA can not to assign dx to pseudo 101 as it already lives through BB 3.

Dump from IRA or passes before it shows:

BB2:
;;  entry block defs     0 [ax] 1 [dx] 2 [cx] 4 [si] 5 [di] 6 [bp] 7 [sp] 16
[argp] 20 [frame] 21 [xmm0] 22 [xmm1] 23 [xmm2] 24 [xmm3] 25 [xmm4] 26 [xmm5]
27 [xmm6] 28 [xmm7] 37 [r8] 38 [\
r9]

;; lr  out       1 [dx] 6 [bp] 7 [sp] 16 [argp] 20 [frame] 83

BB3:
;; lr  in        1 [dx] 6 [bp] 7 [sp] 16 [argp] 20 [frame] 83
;; lr  out       1 [dx] 6 [bp] 7 [sp] 16 [argp] 20 [frame] 83 84

DX lives everywhere.  This info is calculated by DF-infrastructure.

So I think that maintainers of DF-infrastructure should work on this PR from
now on.


  parent reply	other threads:[~2014-06-23 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20  7:47 [Bug rtl-optimization/61572] New: " trippels at gcc dot gnu.org
2014-06-20 11:58 ` [Bug rtl-optimization/61572] " trippels at gcc dot gnu.org
2014-06-23 10:32 ` rguenth at gcc dot gnu.org
2014-06-23 19:50 ` vmakarov at gcc dot gnu.org [this message]
2014-06-24  8:32 ` [Bug tree-optimization/61572] " rguenth at gcc dot gnu.org
2014-06-24  8:35 ` rguenth at gcc dot gnu.org
2014-06-24  8:39 ` rguenth at gcc dot gnu.org
2014-06-24  8:47 ` trippels at gcc dot gnu.org
2014-06-24 10:01 ` rguenth at gcc dot gnu.org
2014-06-24 10:07 ` trippels at gcc dot gnu.org
2014-06-24 10:36 ` rguenth at gcc dot gnu.org
2014-06-24 10:37 ` rguenth 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-61572-4-fk8WVLkx2N@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).