public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Andrew Haley <aph@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Notes from the GROW'10 workshop panel (GCC research opportunities  	workshop)
Date: Thu, 15 Apr 2010 12:15:00 -0000	[thread overview]
Message-ID: <v2y571f6b511004150507w2aaa348alfffe66337a0f2fa2@mail.gmail.com> (raw)
In-Reply-To: <4BC7009D.1060605@redhat.com>

On Thu, Apr 15, 2010 at 2:03 PM, Andrew Haley <aph@redhat.com> wrote:
> On 04/15/2010 12:57 PM, Basile Starynkevitch wrote:
>>
>> Of course I do know about gcj. But I never met any person using it,
>> and I don't know about any person or project really using it (as an
>> example, I am not sure than any Debian or Fedora package is compiled
>> with gcj into a native executable; do you know of many Debian
>> packages compiled with GCJ specifically?).
>
> Lots of them were, but with the availability of OpenJDK and its better
> standard compatibility people are moving packages to it.  There's
> nothing much wrong with the gcj compiler itself, although it does
> generate rather bulky code, but the Classpath libraries on which its
> runtime library depends are not completely Java compatible.

So our computers are spending hours and hours testing Java as part of
the normal bootstrap+regtest cycle -- and nobody even uses it? :-)

(Couldn't resist, sorry! :-)

Ciao!
Steven

  reply	other threads:[~2010-04-15 12:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 14:01 Dorit Nuzman
2010-04-11 18:27 ` Chris Lattner
2010-04-11 19:38   ` Grigori Fursin
2010-04-11 20:25     ` Chris Lattner
2010-04-11 20:58       ` Grigori Fursin
2010-04-14 14:34 ` Grigori Fursin
2010-04-14 14:58   ` Steven Bosscher
2010-04-14 15:21     ` Manuel López-Ibáñez
2010-04-14 15:30       ` Steven Bosscher
2010-04-14 15:36       ` Diego Novillo
2010-04-14 15:50         ` Nathan Froyd
2010-04-14 15:57           ` Richard Guenther
2010-04-14 19:19             ` Tom Tromey
2010-04-14 16:06           ` Diego Novillo
2010-04-14 18:30             ` Richard Guenther
2010-04-14 18:49           ` Toon Moene
2010-04-14 19:52             ` Basile Starynkevitch
2010-04-14 20:31               ` Toon Moene
2010-04-14 20:43               ` Toon Moene
2010-04-14 21:02               ` Ian Lance Taylor
2010-04-14 21:34                 ` Manuel López-Ibáñez
2010-04-15  8:26                 ` Basile Starynkevitch
2010-04-15  8:38                   ` Manuel López-Ibáñez
2010-04-15 12:03                     ` Basile Starynkevitch
2010-04-15 12:07                       ` Andrew Haley
2010-04-15 12:15                         ` Steven Bosscher [this message]
2010-04-15 12:17                           ` Andrew Haley
2010-04-22  9:18                       ` Laurent GUERBY
2010-04-14 21:04               ` Nathan Froyd
2010-04-14 19:42           ` Ian Lance Taylor
2010-04-14 15:44       ` Duncan Sands
2010-04-15  9:05   ` Manuel López-Ibáñez
2010-04-16 12:36     ` Grigori Fursin
2010-04-16 17:15       ` Manuel López-Ibáñez
2010-04-16 17:40         ` Grigori Fursin
2010-04-27 12:40         ` Grigori Fursin
2010-04-27 16:31           ` Manuel López-Ibáñez
2010-04-27 18:42             ` Grigori Fursin

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=v2y571f6b511004150507w2aaa348alfffe66337a0f2fa2@mail.gmail.com \
    --to=stevenb.gcc@gmail.com \
    --cc=aph@redhat.com \
    --cc=gcc@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).