public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: linux-ia64@linux-ia64.org, binutils@sources.redhat.com
Subject: epilogue count exceeds number of nested prologues
Date: Sun, 07 Apr 2002 17:15:00 -0000	[thread overview]
Message-ID: <20020408001714.GA7563@tausq.org> (raw)

Hi all,

While trying to compile mozilla with libffi, the configure phase dies
with a message:

Error: Epilogue count of 4294967296 exceeds number of nested prologues
(0)

I see that this message comes from a patch submitted by David in
February. Is libffi broken? What is needed to fix it?

The offending assembly code is attached. it's the ".restore sp" near
the end that is triggering the error.

thanks
randolph

	.file	"conftest.i"
	.pred.safe_across_calls p1-p5,p16-p63
	.text
	.align 16
	.global main#
	.proc main#
main:
	.prologue 2, 2
	.vframe r2
	mov r2 = r12
	.body
	;;
#APP
	     .data
     .align 8
1:   data8 @fptr(ffi_closure_UNIX)
     data8 1b
     data8 0
     data8 bar
     data8 @fptr(baz)
     data8 quux
     .text
     .global foo
     .proc foo
foo:
     addl r16 = @ltoff(1b), gp;;
     ld8  gp = [r16];;
     ld8  r17 = [gp];;
     ld8  r19 = [r17],8;
	 adds r18 = 16,gp;;
     ld8  r20 = [r17];;
     st8  [r18]=r20;
     mov b6 = r19
     br.cond.sptk.many b6
     .endp

#NO_APP
	;;
	mov r8 = r0
	.restore sp
	mov r12 = r2
	br.ret.sptk.many b0
	.endp main#
	.ident	"GCC: (GNU) 3.0.4"

             reply	other threads:[~2002-04-08  0:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-07 17:15 Randolph Chung [this message]
2002-04-07 22:53 ` Richard Henderson
2002-04-08  8:52 ` [Linux-ia64] " David Mosberger
2002-04-08 10:29 ` David Mosberger
2002-04-08 21:48 ` David Mosberger
2002-04-08 21:55   ` Randolph Chung
2002-04-08 22:57     ` Jeff Licquia

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=20020408001714.GA7563@tausq.org \
    --to=randolph@tausq.org \
    --cc=binutils@sources.redhat.com \
    --cc=linux-ia64@linux-ia64.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).