All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Licquia <jlicquia@progeny.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] epilogue count exceeds number of nested prologues
Date: Tue, 09 Apr 2002 05:56:54 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905425@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905403@msgid-missing>

On Tue, 2002-04-09 at 00:09, Randolph Chung wrote:
> > I'm unable to reproduce this.  If I'm understanding you right, the
> > problem occurred during the configure phase of mozilla (not libffi).
> 
> that's right
> 
> > I just rebuilt Mozilla from the current CVS tree with gcc3.1
> > pre-release and the current CVS binutils.  It built just fine and the
> > resulting binary seems to work flawlessly.
> 
> I'm building from Debian sources. It's possible that it's simply out of
> date (I'm building version 0.9.9).
> 
> > >From the assembly code you provided, it looks as if conftest.c tried
> > to call FFI_STATIC_CLOSURE() from within a function, which can't
> > possibly work.
> 
> indeed, mozilla's configure.in says:
> 
>     if test "$LIBFFI_FOUND" = "yes"; then
>         AC_MSG_CHECKING("for FFI_STATIC_CLOSURE in libffi")
>         AC_TRY_COMPILE([#include "ffi.h"],
>                         [ FFI_STATIC_CLOSURE(foo, bar, baz, quux); ],
>                         [ LIBFFI_HAS_STATIC_CLOSURE=yes ])
>         AC_MSG_RESULT("$result")
>     fi
> 
> which generates (from config.log):
> 
> configure:13494: checking for FFI_STATIC_CLOSURE in libffi
> configure:13503: gcc-3.0 -c -I/home/randolph/debian/mozilla-0.9.9/build-tree/libffi-install/include  -fshort-wchar -pthread -pipe   -I/usr/X11R6/include conftest.c 1>&5
> {standard input}: Assembler messages:
> {standard input}:40: Error: Epilogue count of 4294967296 exceeds number of nested prologues (0)
> configure: failed program was:
> #line 13496 "configure"
> #include "confdefs.h"
> #include "ffi.h"
> int main() {
>  FFI_STATIC_CLOSURE(foo, bar, baz, quux);
> ; return 0; }

I claim responsibility for this code.  For some reason, it worked in
older revisions.

But yes, I can see how that's incorrect, and should be changed.  I can
whip up a patch if no one else is tomorrow.



      parent reply	other threads:[~2002-04-09  5:56 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
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 [this message]

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-105590701905425@msgid-missing \
    --to=jlicquia@progeny.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.