From: Jonathan Larmour <jifl@eCosCentric.com>
To: Mark Salter <msalter@redhat.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>,
ecos-patches@sources.redhat.com
Subject: Re: fix conflict with gcc thread local storage extension
Date: Thu, 20 Mar 2003 18:31:00 -0000 [thread overview]
Message-ID: <3E7A088F.4090403@eCosCentric.com> (raw)
In-Reply-To: <20030320161358.0240A7884D@deneb.localdomain>
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 <msalter@redhat.com>
>>>+
>>>+ * 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
parent reply other threads:[~2003-03-20 18:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030320161358.0240A7884D@deneb.localdomain>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E7A088F.4090403@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@sources.redhat.com \
--cc=ecos-patches@sources.redhat.com \
--cc=msalter@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).