This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
is this an appropriate use of the "target-specific builtin #defines"?
- From: Jonathan Wilson <jonwil at tpgi dot com dot au>
- To: gcc at gnu dot org
- Date: Tue, 21 Oct 2003 09:33:05 +0800
- Subject: is this an appropriate use of the "target-specific builtin #defines"?
Basicly, on win32, __declspec(thread) says "this variable is Thread Specific".
GCC uses __thread in exactly the same way.
Now I have been informed that making __declspec(thread) do the right thing
inside the parser (so that it works as expected) is difficult.
What I want to do (to make things easy) is to add a builtin #define like this:
#define __declspec(thread) __thread
That way, we avoid all the messy stuff in the parser (which is not a good
idea so close to branch for 1.4 (I am trying to avoid changes to non-i386
bits in the hope that the changes are "small enough" to get into 3.4)