This is the mail archive of the
mailing list for the GCC project.
Re: SSA PRE and Open64
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: law at redhat dot com
- Cc: gcc at gcc dot gnu dot org,Eric Christopher <echristo at redhat dot com>
- Date: Wed, 27 Aug 2003 18:46:44 -0400
- Subject: Re: SSA PRE and Open64
- References: <200308272024.h7RKOODm009902@speedy.slc.redhat.com>
On Aug 27, 2003, at 4:24 PM, email@example.com wrote:
In message <firstname.lastname@example.org>, Eric
Quick question, what's the copyright status associated with this code?
It's rewritten based on algorithms in Open64 and the paper.
It's not direct copying of any kind. We couldn't if we wanted to.
Only for clarity.
As with your last update we're now down to the same function names.
If you look at the implementations of most functions, they are quite
I think I can rely upon you to educate me? :)
More importantly, if we're taking code from Open64
or deriving code from
then it not only needs a compatible copyright,
Which it has anyway (It's GPL'd)
but the Open64But we aren't, so we don't need to worry about it.
bits we're using need to be assigned to the the FSF -- which can only
done by the copyright holder on Open64 itself.
If i was writing code that was derivative of what they did, starting
from their code, i would have taken care of all of this before
starting, not later on.