public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47725] [x32] error: unable to find a register to spill in class DIREG
Date: Mon, 14 Feb 2011 14:08:00 -0000	[thread overview]
Message-ID: <bug-47725-4-BgZCs2js77@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47725-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> 2011-02-14 14:06:45 UTC ---
(In reply to comment #4)
> 
> Who generates insn #2?  The machinery handling parameters in function.c?  If
> so, maybe it should do the copy in the incoming mode instead:
> 
> (insn 2 4 3 2 (set (reg/v/f:SI 59 [ pc_target ])
>         (reg:SI 5 di [ pc_target ]))
> 
> (insn 3 5 4 2 (set (reg:DI 60)
>         (zero_extend:DI (reg/v/f:SI 59 [ pc_target ])))

assign_parm_setup_reg has

          enum rtx_code code = unsignedp ? ZERO_EXTEND : SIGN_EXTEND;
          rtx insn, insns;
          HARD_REG_SET hardregs;

          start_sequence ();
          insn = gen_extend_insn (op0, op1, promoted_nominal_mode,
                                  data->passed_mode, unsignedp);
          emit_insn (insn);
          insns = get_insns ();


  parent reply	other threads:[~2011-02-14 14:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14  1:07 [Bug target/47725] New: " hjl.tools at gmail dot com
2011-02-14  1:08 ` [Bug target/47725] " hjl.tools at gmail dot com
2011-02-14  1:31 ` hjl.tools at gmail dot com
2011-02-14  3:18 ` [Bug middle-end/47725] " hjl.tools at gmail dot com
2011-02-14  8:16 ` ebotcazou at gcc dot gnu.org
2011-02-14 14:08 ` hjl.tools at gmail dot com [this message]
2011-02-14 14:21 ` hjl.tools at gmail dot com
2011-02-14 19:01 ` hjl at gcc dot gnu.org
2011-02-14 19:43 ` hjl.tools at gmail dot com
2011-02-15 17:28 ` hjl at gcc dot gnu.org
2011-02-15 20:30 ` hjl at gcc dot gnu.org
2011-02-16 20:22 ` hjl at gcc dot gnu.org
2011-03-18  0:45 ` hjl at gcc dot gnu.org
2011-03-18  5:00 ` hjl at gcc dot gnu.org
2011-04-02  6:04 ` hjl at gcc dot gnu.org
2011-04-02  6:05 ` hjl at gcc dot gnu.org
2011-06-20 14:54 ` hjl at gcc dot gnu.org
2011-06-20 16:02 ` ebotcazou at gcc dot gnu.org
2011-06-20 17:04 ` hjl at gcc dot gnu.org
2011-07-22  6:02 ` pbone at csse dot unimelb.edu.au
2011-07-22  6:07 ` pbone at csse dot unimelb.edu.au
2011-07-28 17:03 ` ubizjak at gmail dot com
2011-07-28 17:07 ` 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-47725-4-BgZCs2js77@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).