public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: yuri@rawbw.com
Cc: java@gcc.gnu.org
Subject: Re: Can gcj be a Java front-end for llvm as well?
Date: Sat, 17 Oct 2009 10:11:00 -0000	[thread overview]
Message-ID: <1255774204.2568.10.camel@hermans.wildebeest.org> (raw)
In-Reply-To: <4AD8D502.1090205@rawbw.com>

On Fri, 2009-10-16 at 13:18 -0700, Yuri wrote:
> The rationale for this is that llvm in many cases produces more optimal 
> code and it's good to have such option if it doesn't come at too high price.

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?

Thanks,

Mark

P.S. There is http://vmkit.llvm.org/ladyvm.html if you need to use
llvm/vmkit. It might not produce the fastest runtime code, but it is a
quick way to mix and match various existing free software projects to
produce something gcj/java-like.

  reply	other threads:[~2009-10-17 10:11 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 [this message]
2009-10-18 22:15   ` Yuri

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=1255774204.2568.10.camel@hermans.wildebeest.org \
    --to=mark@klomp.org \
    --cc=java@gcc.gnu.org \
    --cc=yuri@rawbw.com \
    /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).