Re: Gnutools: consideration for upgrade to GCC 4.6

[Stanislav Meduna <stano at meduna dot org>]

On 15.01.2012 19:42, Sergei Gavrikov wrote:

> Secondly, it lets anyone to use such checks in sources, e.g.
>
>   #if __linux__
>   # include <endian.h>
>   #elif __ecos__
>   # include <machine/endian.h>
>   #else
>   ...
>   #endif

Doing this would break compatibility with older toolchain -
easily fixable (just add another -D... to global CFLAGS),
but nevertheless something every user has to explicitely
address. I don't know what the eCos policy for this kind
of changes is.

I am not strictly against this move (although I am also using
self-compiled toolchains); the question is what does it bring
to the user.

> The third, Why we should avoid to say that eCos is also well known,
> widely used OS?
> ...
> Look on that as a promotion eCos OS.

Does the specification of a target OS belong to a compiler at all?
Is there anything the compiler itself does differently for eCos
than for Linux or RTEMS (that is not covered by other flags)?
If yes, go ahead. If not, frankly, I think that 'promotion' or
'others do it' is a bogus reason for hardcoding something into
a compiler binary, so I'd only do this if there is a technical
reason for it (IMHO of course).

Regards
-- 
                                          Stano