public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Barak Zalstein" <Barak.Zalstein@ParthusCeva.com>
To: <gcc@gcc.gnu.org>
Subject: Re: Dumping RTL???
Date: Thu, 05 Dec 2002 01:07:00 -0000	[thread overview]
Message-ID: <988BE481ACC95C429DCB909F74A3163A0AAF76@exchange-il> (raw)

>> Hmm... gcc is open source... A company like this could ""simply"" alter 
>> gcc to produce complete RTL output and then use their unfree backend 
>> anyways? Given that they release the gcc-patch-source, am I right? Or is 
>> this sceanrio merely academic?
> In fact nobody knows whether this would be legitimate. It has not been
> litigated, and we would just as soon prefer that things stay that way.

Well if it happened to trees (http://open64.sourceforge.net/) why shouldn't it happen to rtx?
It's only a matter of few global variables.

Barak.

             reply	other threads:[~2002-12-05  9:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  1:07 Barak Zalstein [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-08 18:55 Robert Dewar
2002-12-08 11:59 Richard Kenner
2002-12-08  8:16 Richard Kenner
2002-12-08 10:36 ` Daniel Berlin
2002-12-08  7:49 Richard Kenner
2002-12-08  7:25 Robert Dewar
2002-12-08  7:24 Robert Dewar
2002-12-04 21:18 Robert Dewar
2002-12-04 19:22 Richard Kenner
2002-12-08  7:23 ` Marc Espie
2002-12-04 15:57 Chris Lattner
2002-12-03  7:37 Robert Dewar
2002-12-02 21:52 Chris Lattner
2002-12-02 20:39 gyanindra mishra
2002-12-03  3:00 ` Andrew Haley
2002-12-03  4:13   ` Fabio Alemagna
2002-12-03 11:36     ` Joe Buck
2002-12-04 15:13   ` Svein E. Seldal
2002-12-08  7:17     ` Marc Espie
2002-12-02  6:57 Robert Dewar
2002-12-02  6:01 gyanindra mishra

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=988BE481ACC95C429DCB909F74A3163A0AAF76@exchange-il \
    --to=barak.zalstein@parthusceva.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).