public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55597] [4.8 Regression] internal compiler error: in plus_constant, at explow.c:88
Date: Tue, 04 Dec 2012 23:25:00 -0000	[thread overview]
Message-ID: <bug-55597-4-wyLUTX4sUU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55597-4@http.gcc.gnu.org/bugzilla/>


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

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steven at gcc dot gnu.org
          Component|middle-end                  |target

--- Comment #3 from Steven Bosscher <steven at gcc dot gnu.org> 2012-12-04 23:24:41 UTC ---
Out of expand GCC produces:

(insn 6 5 7 2 (set (reg:DI 61)
        (reg:DI 0 ax)) t.c:8 -1
     (expr_list:REG_EQUAL (symbol_ref:SI ("__morestack_initial_sp") \
   [flags 0x10]  <var_decl 0x7ffff6263720 __morestack_initial_sp>)
        (nil)))
(insn 7 6 8 2 (parallel [
            (set (reg:DI 62)
                (plus:DI (reg:DI 61)
                    (const_int 4 [0x4])))
            (clobber (reg:CC 17 flags))
        ]) t.c:8 -1
     (nil))

In alias.c, the compiler tries to simplify r62=r61+4 to
r62=symbol_ref:SI ("__morestack_initial_sp")+4 but plus_constant
doesn't accept symbol_ref:SI ("__morestack_initial_sp") because it
is is SImode but should be DImode.

Back-end bug, I'm guessing something Pmode related.


  parent reply	other threads:[~2012-12-04 23:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-04 21:01 [Bug middle-end/55597] New: " hjl.tools at gmail dot com
2012-12-04 22:29 ` [Bug middle-end/55597] " hjl.tools at gmail dot com
2012-12-04 22:52 ` bonzini at gnu dot org
2012-12-04 23:25 ` steven at gcc dot gnu.org [this message]
2012-12-04 23:46 ` [Bug target/55597] " steven at gcc dot gnu.org
2012-12-04 23:50 ` [Bug middle-end/55597] " hjl.tools at gmail dot com
2012-12-05 11:34 ` [Bug middle-end/55597] [4.8 Regression] " ebotcazou at gcc dot gnu.org
2012-12-05 17:28 ` hjl.tools at gmail dot com
2012-12-05 17:56 ` hjl.tools at gmail dot com
2012-12-05 20:46 ` ubizjak at gmail dot com
2012-12-06  0:22 ` hjl.tools at gmail dot com
2012-12-06 15:05 ` jakub at gcc dot gnu.org
2012-12-06 20:14 ` ubizjak at gmail dot com
2012-12-06 22:05 ` uros at gcc dot gnu.org
2012-12-07  3:44 ` hjl.tools at gmail dot com
2012-12-07  8:11 ` uros at gcc dot gnu.org
2012-12-07  8:21 ` ubizjak at gmail dot com

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-55597-4-wyLUTX4sUU@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).