From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] epilogue count exceeds number of nested prologues
Date: Mon, 08 Apr 2002 17:25:05 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905409@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905403@msgid-missing>
>>>>> On Sun, 7 Apr 2002 17:17:14 -0700, Randolph Chung <randolph@tausq.org> said:
Randolph> Hi all, While trying to compile mozilla with libffi, the
Randolph> configure phase dies with a message:
Randolph> Error: Epilogue count of 4294967296 exceeds number of
Randolph> nested prologues (0)
Randolph> I see that this message comes from a patch submitted by
Randolph> David in February. Is libffi broken? What is needed to fix
Randolph> it?
I now realize that you must have been using the latest binutils, as the
old one silently generated bad unwind info.
As Richard pointed out in his mail, the offending code really is
broken. I was planning to update the mozilla libffi anyhow, both to
sync up with Hans's recent unwind fixes and to look into whether we
could use the assembler directives added for C++ vtables to simplify
the generation of static closures. Let me take a look at it.
--david
next prev parent reply other threads:[~2002-04-08 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 0:17 [Linux-ia64] epilogue count exceeds number of nested prologues Randolph Chung
2002-04-08 15:52 ` David Mosberger
2002-04-08 17:25 ` David Mosberger [this message]
2002-04-09 4:46 ` David Mosberger
2002-04-09 5:00 ` David Mosberger
2002-04-09 5:09 ` Randolph Chung
2002-04-09 5:23 ` Randolph Chung
2002-04-09 5:56 ` 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=marc-linux-ia64-105590701905409@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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