From: abhishek desai <abhi00@gmail.com>
To: java@gcc.gnu.org
Subject: FFI closure on mips
Date: Mon, 12 Oct 2009 15:49:00 -0000 [thread overview]
Message-ID: <898285d30910120849v771f35f7pb13675e261490dfb@mail.gmail.com> (raw)
Hi,
I am compiling sources of gcc 3.4.6 with libgcj interpreter support
for the mipsel platform. When compiling with --enable-interpreter flag
I get a compilation error in the file resolve.cc in function
void * _Jv_InterpMethod::ncode ()
when it tries to use the ffi_raw_closure structure. The usage is not
under any #ifdef.
In newer versions of gcc this function is in interpret.cc.
This structure is defined in the ffi.h header file of libffi under the
flag FFI_CLOSURES.
FFI_CLOSURES is defined for each target. For mips it is defined as
#define FFI_CLOSURES 0
Is ffi closure necessay for libgcj compilation ? Can we compile libgcj
without the ffi closure support ?
How can I get it compiled on a mipsel system ?
I have to use gcc 3.4.6 since it is a project requirement.
--- abhi
next reply other threads:[~2009-10-12 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 15:49 abhishek desai [this message]
2009-10-12 16:02 ` Bryce McKinlay
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=898285d30910120849v771f35f7pb13675e261490dfb@mail.gmail.com \
--to=abhi00@gmail.com \
--cc=java@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).