From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19081 invoked by alias); 15 Jan 2012 21:39:58 -0000 Received: (qmail 19073 invoked by uid 22791); 15 Jan 2012 21:39:57 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from www.meduna.org (HELO meduna.org) (92.240.244.38) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 15 Jan 2012 21:39:45 +0000 Received: from [178.143.125.248] (helo=[192.168.130.22]) by meduna.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1RmXnZ-0001qT-8i for ecos-devel@ecos.sourceware.org; Sun, 15 Jan 2012 22:39:42 +0100 Message-ID: <4F13478E.2040106@meduna.org> Date: Sun, 15 Jan 2012 21:39:00 -0000 From: Stanislav Meduna User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: ecos-devel@ecos.sourceware.org Subject: Re: Gnutools: consideration for upgrade to GCC 4.6 References: <4F106345.4080902@siva.com.mk> <4F11574D.9070002@dallaway.org.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Authenticated-User: stano@meduna.org X-Authenticator: dovecot_plain X-Spam-Score: -6.9 X-Spam-Score-Int: -68 X-Exim-Version: 4.72 (build at 12-May-2011 18:13:45) X-Date: 2012-01-15 22:39:42 X-Connected-IP: 178.143.125.248:53657 X-Message-Linecount: 51 X-Body-Linecount: 38 X-Message-Size: 1910 X-Body-Size: 1230 X-Received-Count: 1 X-Recipient-Count: 1 X-Local-Recipient-Count: 1 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2012-01/txt/msg00017.txt.bz2 On 15.01.2012 19:42, Sergei Gavrikov wrote: > Secondly, it lets anyone to use such checks in sources, e.g. > > #if __linux__ > # include > #elif __ecos__ > # include > #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