On 12/19/14 15:33, Eric Botcazou wrote:
Revision version, the divmod and the parity routines have been reimplemented
based on libgcc2.c and all the new files are now under GPL+exception.
libgcc/ChangeLog
2014-12-19 Eric Botcazou
* config.host: Add Visium support.
* config
Revision version, the divmod and the parity routines have been reimplemented
based on libgcc2.c and all the new files are now under GPL+exception.
libgcc/ChangeLog
2014-12-19 Eric Botcazou
* config.host: Add Visium support.
* config/visium: New directory.
--
Eric
> Well, you'll need FSF approval to relicense - and unless you want to keep
> the same sources used verbatim in both places, the GPL+exception notice is
> the obvious one given such approval. (But in any case, putting in LGPL
> files without a license exception seems a bad idea, because it goes
>
On Mon, 15 Dec 2014, Eric Botcazou wrote:
> > Do you have a reason for using fp-bit instead of soft-fp?
>
> Apart from the obvious historical reason, probably not, but recently added
> ports (Blackfin, Epiphany) also use it so I'm not sure we want to change it.
I doubt they have any good reason
> Do you have a reason for using fp-bit instead of soft-fp?
Apart from the obvious historical reason, probably not, but recently added
ports (Blackfin, Epiphany) also use it so I'm not sure we want to change it.
> libgcc files are generally GPL+exception, not LGPL without exception with
> a very
Do you have a reason for using fp-bit instead of soft-fp?
libgcc files are generally GPL+exception, not LGPL without exception with
a very old FSF address (config/visium/div64.c, mod64.c,
set_trampoline_parity.c, udiv64.c, udivmod64.c, umod64.c)
--
Joseph S. Myers
jos...@codesourcery.com
