From: Jim Wilson <wilson@cygnus.com>
To: mrs@wrs.com (Mike Stump)
Cc: egcs@cygnus.com
Subject: Re: intel 960 support Was: pentium?
Date: Thu, 02 Oct 1997 19:43:00 -0000 [thread overview]
Message-ID: <199710030243.TAA15610@cygnus.com> (raw)
In-Reply-To: <199710012026.NAA01338@kankakee.wrs.com>
> There is also the issue of copyright assignments. We can't use
> Intel's code without a copyright assignment from Intel. I am not
> sure how hard it will be to get one; it might be easier to just
> write new code from scratch in some cases.
Maybe not that hard... Below is what's on file already.
Except that none of these assignments are useful. All of the existing
assignments are restricted to a particular patch or release, and the most
recent i960 related one is from 6 years ago. If I wanted to, I could add
changes from a 6 year old GNU960 release, but I can not add changes from the
most recent GNU960 release. I am really not very interested in 6 year old
sources.
What would be really useful is if Intel assigned all past/future i960 gcc
related changes to the FSF, but I seriously doubt that will happen.
I do believe that we can get an assignment for a particular GNU960 release
from Intel, because they have signed assignments in the past. However, it
will take work on our part to get the assignment, because Intel is not going
to volunteer it. And we will need to get another assignment everytime Intel
makes another GNU960 release. It isn't clear if all of this work is
worthwhile.
Jim
next prev parent reply other threads:[~1997-10-02 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-01 13:26 Mike Stump
1997-10-02 19:43 ` Jim Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-01 5:27 pentium? Neal Becker
1997-10-01 6:30 ` pentium? Joel Sherrill
1997-10-01 8:39 ` intel 960 support Was: pentium? Robert Lipe
1997-10-01 12:21 ` Jim Wilson
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=199710030243.TAA15610@cygnus.com \
--to=wilson@cygnus.com \
--cc=egcs@cygnus.com \
--cc=mrs@wrs.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).