public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.org>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: "Nathan Froyd" <froydnj@codesourcery.com>,
	"Diego Novillo" <dnovillo@google.com>,
	"Manuel López-Ibáñez" <lopezibanez@gmail.com>,
	"Steven Bosscher" <stevenb.gcc@gmail.com>,
	"Grigori Fursin" <gfursin@gmail.com>,
	"Dorit Nuzman" <DORIT@il.ibm.com>,
	gcc@gcc.gnu.org
Subject: Re: Notes from the GROW'10 workshop panel (GCC research 	opportunities     workshop)
Date: Wed, 14 Apr 2010 20:43:00 -0000	[thread overview]
Message-ID: <4BC62610.7090208@moene.org> (raw)
In-Reply-To: <4BC61C34.7070106@starynkevitch.net>

Basile Starynkevitch wrote:

> Toon Moene wrote:
>>
>> Mutatis mutandis, the same goes for GCC: There might be too many 
>> hurdles to use GCC in academia.  
> 
> This is probably true, however, the plugin ability of the just released 
> GCC 4.5 (or is it released tomorrow) helps probably significantly.

> My point is that academics can quite easily contribute to GPL software, 
> but much harder obtain the necessary legal authorizations to transfer 
> copyright to FSF. 

My answer was not as clear as necessary.  My (earlier) argument was from 
the perspective of the providers of the code (GCC) - it did not take 
into account those who *want* to contribute to GCC, but have a hard time 
to convince their respective legal departments (whether in academia or 
the commercial world).

In that case, a clear plugin interface (and accompanying documentation) 
can be instrumental in proving that an improvement "actually does the 
desired thing" and hence can be considered "the outcome of the academic 
research" (which then subsequently can be written up in a paper).

Thanks for pointing that out.

-- 
Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
At home: http://moene.org/~toon/
Progress of GNU Fortran: http://gcc.gnu.org/gcc-4.5/changes.html

  parent reply	other threads:[~2010-04-14 20:31 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 [this message]
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
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=4BC62610.7090208@moene.org \
    --to=toon@moene.org \
    --cc=DORIT@il.ibm.com \
    --cc=basile@starynkevitch.net \
    --cc=dnovillo@google.com \
    --cc=froydnj@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gfursin@gmail.com \
    --cc=lopezibanez@gmail.com \
    --cc=stevenb.gcc@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).