From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25507 invoked by alias); 20 Mar 2003 18:31:18 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 25490 invoked from network); 20 Mar 2003 18:31:18 -0000 Message-ID: <3E7A088F.4090403@eCosCentric.com> Date: Thu, 20 Mar 2003 18:31:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.2) Gecko/20021203 X-Accept-Language: en-gb, en, en-us MIME-Version: 1.0 To: Mark Salter Cc: eCos Maintainers , ecos-patches@sources.redhat.com Subject: Re: fix conflict with gcc thread local storage extension References: <20030320160732.7B5C07884D@deneb.localdomain> <1048176638.9579.9701.camel@hermes.chez-thomas.org> <20030320161358.0240A7884D@deneb.localdomain> In-Reply-To: <20030320161358.0240A7884D@deneb.localdomain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00044.txt.bz2 Mark Salter wrote: >>>>>>Gary Thomas writes: > > >>On Thu, 2003-03-20 at 09:07, Mark Salter wrote: >> >>>Index: compat/posix/current/ChangeLog >>>=================================================================== >>>RCS file: /cvs/ecos/ecos/packages/compat/posix/current/ChangeLog,v >>>retrieving revision 1.43 >>>diff -u -p -5 -r1.43 ChangeLog >>>--- compat/posix/current/ChangeLog 19 Mar 2003 14:17:20 -0000 1.43 >>>+++ compat/posix/current/ChangeLog 20 Mar 2003 16:05:01 -0000 >>>@@ -1,5 +1,10 @@ >>>+2003-03-20 Mark Salter >>>+ >>>+ * include/pthread.h: Avoid conflict with recently introduced gcc >>>+ __thread keyword. >>>+ > > >>Wasn't that sweet of them? What version does this show up in? > > I'm seeing it in a 3.3 variant. I think it went into CVS around > the December time frame. Ouch. I wish they'd realise that they can't just add commonly occurring words to the namespace and think they can get away with it just because it's got "__" prepended, when it means many OS's will have to suffer. This should go in the 2.0 branch too (maintainer list CC'd). The alternative is that upcoming GCC 3.3 will barf on eCos 2.0. This is also obviously a trivially benign change. Jifl -- eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine