If I'm right, here are copyright assignments to FSF for the Microchip's
contributions for GCC.

Best regards,

Francois Poulain

[EMAIL 
PROTECTED]/David/Install/gcc-3.3_with_PIC30_support/gcc-3.3/gcc/config/pic30 $ 
head pic30.*

==> pic30.c <==
/* Subroutines for insn output for Microchip dsPIC30.
   Copyright (C) 1994, 1995, 1996, 1997, 1998 Free Software Foundation,
Inc.
   Contributed by John Elliott ([EMAIL PROTECTED])

This file is part of GNU CC.

GNU CC is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 1, or (at your option)
any later version.

==> pic30.h <==
#ifndef _PIC30_H_
#define _PIC30_H_

/* Definitions of target machine for GNU compiler.
   Copyright (C) 1994, 95-98, 1999 Free Software Foundation, Inc.
   Contributed by Microchip.

This file is part of GNU CC.

GNU CC is free software; you can redistribute it and/or modify

==> pic30.md <==
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;;- Machine description for GNU compiler
;;- Microchip dsPIC30 version.
;; Copyright (C) 1994, 1995, 1996, 1997 Free Software Foundation, Inc.

;; Contributed by John Elliott ([EMAIL PROTECTED])

;; This file is part of GNU CC.

;; GNU CC is free software; you can redistribute it and/or modify


Le dimanche 09 avril 2006 à 05:39 -0500, Aaron W. LaFramboise a écrit :
> François Poulain wrote:
> 
> > I think so. Microchip have done a modified version of GCC-3.3 with
> > DSPICs support, so we have got a heavy good base to work on the
> > instruction set, wich is similar for PIC18. DSPIC is a 16 bit CPU, so is
> > memory isn't segmented.
> 
> Just as a reminder, even though the Microchip code is covered by the 
> GPL, code based on it won't be acceptable for inclusion into FSF GCC 
> unless you can get Microchip to sign a copyright assignment, which seems 
> unlikely.  Any code in FSF GCC needs to be written by someone with a 
> copyright assignment to FSF, or at least a public domain release.  (I'm 
> not sure on the exact rules here.  Someone at the FSF would know exactly.)
> 

Reply via email to