public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.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:03:00 -0000	[thread overview]
Message-ID: <20100415115737.GA32020@hector.lesours> (raw)
In-Reply-To: <u2x6c33472e1004150126sf210939se5e8d1acf1d35d5c@mail.gmail.com>

On Thu, Apr 15, 2010 at 10:26:16AM +0200, Manuel López-Ibáñez wrote:
> On 14 April 2010 23:34, Basile Starynkevitch <basile@starynkevitch.net> wrote:
> >
> > And my personal preference on GCC licensing would be more a Linux-kernel
> > like GPL with copyright belonging to authors employee (I don't feel a SCO
> > like issue as a major threat today; it might have been ten years ago). That
> > is much easier to get than a copyright transfer to FSF.
> 
> I am sorry but I do not think the copyright transfer/ GCC license is
> worth discussing in this list. 

Then sorry for having discussed it. It was only my personal option.
Discussion closed.

> 
> And given the feedback provided by Grigori, the licensing issues are
> very low in the list of complains from academia and the major
> complaints are technical (speed, simplicity, and documentation).
> 
> > And GCC is probably less threatened today by legal issues Ä… la SCO than by
> > obesity, obsolescence, outside competition -eg LLVM- and perhaps even less
> > interest by industry for the low level languages (C, C++, Ada) GCC is
> > processing. Even in industry, scripting languages (or languages like Java or
> > C# which are not practically significant for GCC) have more market share
> > than a dozen years ago.
> 
> You know there is a Java FE in GCC, don't you?


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?). But I don't know much about Java (except practically Sun's
JVM, IBM's one, and OpenJdk).

> 
> And whether a language is significant or not for GCC is a question of
> someone contributing a FE for it. 

I did not meant significant for GCC, I did meant significant for industrial
use (outside of the GCC community). What I just believe is that programming
languages usually compiled by GCC are a bit less used than ten years ago (in
favor of scripting languages such as PHP). And it is the industrial
importance of languages which I believe determine indirectly the work on GCC
(because industrials are funding directly or indirectly, or at least are
lobbying for, most of the labor put into GCC)

> And calling Ada "low-level"... Honestly, let's stop this sub-thread
> here. No more discussion about plugins or legal issues, please.


Ok. Sorry for the inconvenience.

(BTW I call lowlevel any language which does not manage memory
automatically; I am quite fond of Ocaml even if I don't use it much today.
So in my eyes C++, Ada95 & Fortran2005 are still low-level; this is only a
matter of taste & terminology).

Cheers

-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***

  reply	other threads:[~2010-04-15 11:57 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 [this message]
2010-04-15 12:07                       ` Andrew Haley
2010-04-15 12:15                         ` Steven Bosscher
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=20100415115737.GA32020@hector.lesours \
    --to=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    --cc=lopezibanez@gmail.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).