Re: Gnutools: consideration for upgrade to GCC 4.6

["Bernard Fouché" <bernard.fouche@kuantic.com>]

Le 16/01/2012 22:11, Sergei Gavrikov a écrit :
> On Mon, 16 Jan 2012, Sergei Gavrikov wrote:
>
>> I hope I have convinced you and Stano that I did not suggest to "close"
>> eCos sources by __ecos__ checks. More that to propagate that built-in
>> definition is only a few lines for GCC patch and if that is issue I am
>> ready to withdraw my "I like their built-in" :-)
> Nobody (me too) said (thought) about:
>
>    http://www.ecoscentric.com/trademark_usage.shtml
>
> AIANL. So, I actually withdraw my "wish" as [eCos] is registered
> trademark and anyone would use our patches and abuse the word.
>
> Sergei

Being able to identify/check the toolchain used seems a very good idea. 
Why not ask eCosCentric about the legal issue? They already make a 
toolchain available for public eCos, that can be installed with the 
installation tool (see http://ecos.sourceware.org/getstart.html) . IMHO 
it is in the interest of eCos to avoid having its public image altered 
because of bugs that are related to the toolchain and not eCos itself.

The message from Tomas is a perfect example of such a need:

Le 17/01/2012 10:36, Tomas Frydrych a écrit :
> Some of the more recent gccs were not producing usable binaries on some
> platforms (including arm) with the -Os option. I do not know if this is
> the case with 4.6.2, and I don't think ecos uses -Os by default, but it
> is probably worth checking whether this works (and at least documenting
> somewhere if it does not).
>
> Tomas

     Bernard