From: Yuri <yuri@rawbw.com>
To: Mark Wielaard <mark@klomp.org>
Cc: java@gcc.gnu.org
Subject: Re: Can gcj be a Java front-end for llvm as well?
Date: Sun, 18 Oct 2009 22:15:00 -0000 [thread overview]
Message-ID: <4ADB9393.1060704@rawbw.com> (raw)
In-Reply-To: <1255774204.2568.10.camel@hermans.wildebeest.org>
Mark Wielaard wrote:
> When gcj/gcc produces sub-optimal code wouldn't it make more sense to
> just fix gcj? Can you give some examples of such code?
>
It does make sense to fix gcj and gcc.
However, since gcj only connects to gcc for code generation, it can also
serve as a java frontend for llvm.
llvm obviously needs Java frontend (just like frontends for other common
languages). And why to redevelop it from scratch, if gcj is almost a
perfect fit?
I can't give a particular example of performance here now. But pretty
much every time when I compiled large (c++) project with llvm I got
better runtime compared to gcc. Usually 10-20%.
I don't try to put blame on gcc here. I am just saying that the more
uses gcj finds the better.
Yuri
prev parent reply other threads:[~2009-10-18 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 20:18 Yuri
2009-10-17 10:11 ` Mark Wielaard
2009-10-18 22:15 ` Yuri [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=4ADB9393.1060704@rawbw.com \
--to=yuri@rawbw.com \
--cc=java@gcc.gnu.org \
--cc=mark@klomp.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).