From: Jeff Law <law@redhat.com>
To: Alex Turjan <aturjan@yahoo.com>
Cc: gcc@gcc.gnu.org
Subject: Re: reload question
Date: Wed, 23 Jun 2010 18:30:00 -0000 [thread overview]
Message-ID: <4C2243D9.9030802@redhat.com> (raw)
In-Reply-To: <449357.18702.qm@web62407.mail.re1.yahoo.com>
On 06/23/10 11:22, Alex Turjan wrote:
> Hi,
> My port supports hardware loops generated by the following (do_end) pattern:
>
> (set (pc) (if_then_else (ne (match_operand:HI 0 "general_register_operand" "d")
> (const_int 0))
> (label_ref (match_operand 1 "" ""))
> (pc)))
> (set (match_operand:HI 2 "general_register_operand" "=0")
> (plus:HI (match_operand:HI 3 "general_register_operand" "0")
> (const_int -1)))
> (clobber (match_operand:BI 4 "predicate_register_operand" "=j"))
>
>
> When Im compiling a loop with high register pressure the register allocator does not allocate a register for the loop counter (i.e., operand 0) as it has a long life range. Thus operand 0 has to be reloaded but then I get a failure in the reload:
>
> error: unable to generate reloads for:
> (jump_insn 211 182 188 11 lib5.c:51 (parallel [
> (set (pc)
> (if_then_else (ne (reg:HI 292 [ N ])
> (const_int 0 [0x0]))
> (label_ref 183)
> (pc)))
> (set (reg:HI 292 [ N ])
> (plus:HI (reg:HI 292 [ N ])
> (const_int -1 [0xffffffffffffffff])))
> (clobber (reg:BI 33 p1 [293]))
> ]) 506 {do_endhi} (expr_list:REG_UNUSED (reg:BI 33 p1 [293])
> (expr_list:REG_BR_PROB (const_int 9100 [0x238c])
> (nil)))
> -> 183)
> lib5.c:105:1: internal compiler error: in find_reloads, at reload.c:3821
>
> Can anybody give me a hint?
> I am aware of the following msg:
> http://gcc.gnu.org/ml/gcc/2001-09/msg00942.html
> but still dont know how to make reload do the work.
>
insns which branch are not allowed to have output reloads. You must
support any kind of register as well as memory operands in your insn for
the loop counter.
Jeff
next prev parent reply other threads:[~2010-06-23 17:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 17:41 Alex Turjan
2010-06-23 18:30 ` Jeff Law [this message]
2010-06-23 21:29 ` Alex Turjan
2010-06-23 21:43 ` Jeff Law
2010-06-24 3:44 ` Joern Rennecke
-- strict thread matches above, loose matches on Subject: below --
2011-08-11 16:49 Hari Sandanagobalane
2007-08-10 20:02 Pat Haugen
2007-08-11 0:18 ` Ian Lance Taylor
2007-08-13 14:55 ` Pat Haugen
2007-08-13 17:42 ` Ian Lance Taylor
2007-08-11 11:45 ` Paolo Bonzini
2005-03-16 10:08 Miles Bader
2005-03-16 14:58 ` Bernd Schmidt
2005-03-18 10:35 ` Miles Bader
2005-03-18 14:04 ` Miles Bader
2005-03-22 18:56 ` Ian Lance Taylor
2005-03-25 14:27 ` tm_gccmail
2005-03-25 15:43 ` Ian Lance Taylor
2005-06-02 5:56 ` Miles Bader
2005-03-25 16:30 ` Alan Lehotsky
2003-03-19 12:51 Reload question Joern Rennecke
2003-03-19 19:39 ` Eric Botcazou
2003-03-18 0:25 Eric Botcazou
2002-07-25 13:57 Richard Kenner
2002-07-26 13:35 ` Mark Mitchell
2002-07-26 15:01 ` Bernd Schmidt
2002-07-26 16:35 ` Mark Mitchell
2002-07-25 13:47 Mark Mitchell
2002-07-25 16:19 ` Bernd Schmidt
2002-01-27 4:34 reload question Chris Lattner
1997-09-29 5:34 Reload question Christian Iseli
1997-09-29 8:41 ` Jeffrey A Law
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=4C2243D9.9030802@redhat.com \
--to=law@redhat.com \
--cc=aturjan@yahoo.com \
--cc=gcc@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).