From: Adam Sampson <ats1@ukc.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: non-gcc linux?
Date: Mon, 6 Nov 2000 23:14:56 +0000 [thread overview]
Message-ID: <20001106231456.A14197@cartman.ukc.ac.uk> (raw)
In-Reply-To: <fa.fvk85sv.1oigpiv@ifi.uio.no> <fa.cq7bdsv.gggbio@ifi.uio.no> <ylu29mey6f.fsf@windlord.stanford.edu> <3A0602E9.D59F2E50@Rikers.org>
In-Reply-To: <3A0602E9.D59F2E50@Rikers.org>; from Tim@Rikers.org on Sun, Nov 05, 2000 at 06:01:29PM -0700
On Sun, Nov 05, 2000 at 06:01:29PM -0700, Tim Riker wrote:
> In short the impact of adding code to gcc that is not copyright FSF is
> minimal. Only the FSF copyrighted code would be defensible by the FSF. Any
> other code GPL violations would be the responsibility of the copyright
> owners to defend.
Just as a minor point: pro64 _does_ use GCC code. It's effectively the GCC
frontend stuck together with the SGI backend, with a translation layer in
the middle to translate between the intermediate code formats that the two
compilers use. There are some fairly entertaining "this is a gruesome hack"
comments in the source code.
--
Adam Sampson
azz@gnu.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-06 23:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fvk85sv.1oigpiv@ifi.uio.no>
[not found] ` <fa.cq7bdsv.gggbio@ifi.uio.no>
2000-11-06 0:34 ` Russ Allbery
2000-11-06 1:01 ` Tim Riker
2000-11-06 23:14 ` Adam Sampson [this message]
2000-11-04 5:34 non-gcc linux? (was Re: Where did kgcc go in 2.4.0-test10?) Aaron Sethman
2000-11-04 9:18 ` non-gcc linux? Tim Riker
2000-11-04 10:58 ` Alan Cox
2000-11-05 20:52 ` Tim Riker
2000-11-05 21:06 ` Jakub Jelinek
2000-11-05 21:18 ` Tim Riker
2000-11-05 22:42 ` Marc Lehmann
2000-11-05 23:05 ` Tim Riker
2000-11-06 0:05 ` Marc Lehmann
2000-11-06 8:53 ` Thomas Pornin
2000-11-05 23:26 ` Ion Badulescu
2000-11-06 6:34 ` Eric W. Biederman
2000-11-05 22:46 ` Alan Cox
2000-11-05 22:45 ` Alan Cox
2000-11-05 22:52 ` Tim Riker
2000-11-04 12:20 ` Kai Henningsen
-- strict thread matches above, loose matches on Subject: below --
2000-11-04 4:25 Bryan Sparks
2000-11-02 21:06 non-gcc linux? (was Re: Where did kgcc go in 2.4.0-test10?) Christoph Hellwig
2000-11-02 21:21 ` non-gcc linux? Tim Riker
2000-11-02 21:04 non-gcc linux? (was Re: Where did kgcc go in 2.4.0-test10?) Tim Riker
2000-11-02 21:17 ` Alan Cox
2000-11-02 21:23 ` Andi Kleen
2000-11-02 21:27 ` non-gcc linux? Tim Riker
2000-11-02 21:41 ` Andi Kleen
2000-11-02 21:43 ` Tim Riker
2000-11-03 7:21 ` Gábor Lénárt
2000-11-04 11:39 ` Kai Henningsen
2000-11-02 18:55 non-gcc linux? (was Re: Where did kgcc go in 2.4.0-test10?) Tim Riker
2000-11-02 19:07 ` Alan Cox
2000-11-02 19:18 ` Andi Kleen
2000-11-02 19:17 ` non-gcc linux? Tim Riker
2000-11-02 19:52 ` Andrea Arcangeli
2000-11-02 20:00 ` Tim Riker
2000-11-02 20:29 ` Andrea Arcangeli
2000-11-02 22:23 ` D. Hugh Redelmeier
2000-11-02 22:31 ` Jeff Garzik
2000-11-03 22:02 ` D. Hugh Redelmeier
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=20001106231456.A14197@cartman.ukc.ac.uk \
--to=ats1@ukc.ac.uk \
--cc=azz@gnu.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®