This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Internal compiler error -- unrecognizable insn.
- To: dkorn at pixelpower dot com, gcc at gcc dot gnu dot org
- Subject: Re: Internal compiler error -- unrecognizable insn.
- From: Mike Stump <mrs at windriver dot com>
- Date: Thu, 30 Nov 2000 12:13:38 -0800 (PST)
> From: David Korn <dkorn@pixelpower.com>
> To: "'gcc@gcc.gnu.org'" <gcc@gcc.gnu.org>
> Date: Thu, 30 Nov 2000 14:18:48 -0000
> textline.cpp: In function `void TextLineStyleChanged()':
> textline.cpp:389: internal error--unrecognizable insn:
> (call_insn/i 274 273 345 (parallel[
> (set (reg:SI 3 r3)
> (call (mem:SI (symbol_ref:SI ("AddCharacterLine__FUi")) 0)
> (const_int 0 [0x0])))
> (use (const_int 0 [0x0]))
> (clobber (scratch:SI))
> ] ) -1 (insn_list 273 (nil))
> (expr_list:REG_UNUSED (reg:SI 3 r3)
> (expr_list:REG_UNUSED (scratch:SI)
> (nil)))
> (expr_list (use (reg:SI 3 r3))
> (nil)))
> make: *** [textline.o] Error 0x1
Check for the constraints and the conditions on the various insns that
have call anywhere in them, between top of tree and your 2.95.2 tree.
Look for this type of change:
***************
*** 3735,3742 ****
(define_expand "movsfcc"
[(set (match_operand:SF 0 "gpc_reg_operand" "=f")
(if_then_else:SF (match_operand 1 "comparison_operator" "")
! (match_operand:SF 2 "gpc_reg_operand" "f")
! (match_operand:SF 3 "gpc_reg_operand" "f")))]
"TARGET_PPC_GFXOPT && TARGET_HARD_FLOAT"
"
{
--- 3735,3742 ----
(define_expand "movsfcc"
[(set (match_operand:SF 0 "gpc_reg_operand" "=f")
(if_then_else:SF (match_operand 1 "comparison_operator" "")
! (match_operand:SF 2 "gpc_reg_operand" "")
! (match_operand:SF 3 "gpc_reg_operand" "")))]
"TARGET_PPC_GFXOPT && TARGET_HARD_FLOAT"
"
{
If you find something like that, then that might be what you need. If
that isn't it, then I don't know quite what the problem is.
> 4) How can you use the testsuite with a non-self-hosted port?
Yes, we do. See my diffs for changes to dejagnu. If you don't have
them, I'd be happy to email them to you. They are large (3M), make
sure you can handle slightly larger email first.