--- Comment #7 from dnovillo at gcc dot gnu dot org 2005-10-21 18:59
---
Fixed. http://gcc.gnu.org/ml/gcc-patches/2005-10/msg01311.html
--
dnovillo at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #6 from cvs-commit at gcc dot gnu dot org 2005-10-21 18:57
---
Subject: Bug 24455
CVSROOT:/cvs/gcc
Module name:gcc
Branch: gomp-20050608-branch
Changes by: [EMAIL PROTECTED]2005-10-21 18:57:39
Modified files:
gcc: ChangeLog.g
--- Comment #5 from dnovillo at gcc dot gnu dot org 2005-10-20 17:52
---
The problem here is that when we are parsing the second declaration, we call
start_decl before having parsed the threadprivate clause. This causes us to
miss the attribute.
One solution I'm considering is to look
--- Comment #4 from dnovillo at redhat dot com 2005-10-20 17:07 ---
Subject: Re: [gomp] Trouble with threadprivate and extern
On Thursday 20 October 2005 12:50, reichelt at igpm dot rwth-aachen dot de
> Doesn't translation unit cover the include file?
>
> But anyway. How should I mark
On Thursday 20 October 2005 12:50, reichelt at igpm dot rwth-aachen dot de
> Doesn't translation unit cover the include file?
>
> But anyway. How should I mark it threadprivate in file2.c?
> Adding "#pragma omp threadprivate (i)" before or after "int i;"
> doesn't work.
>
Indeed, sorry about that.
--- Comment #3 from reichelt at igpm dot rwth-aachen dot de 2005-10-20
16:50 ---
Subject: Re: [gomp] Trouble with threadprivate and extern
On 20 Oct, dnovillo at redhat dot com wrote:
>
>
> --- Comment #1 from dnovillo at redhat dot com 2005-10-20 16:45 ---
> Subject: Re:
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-10-20 16:49 ---
(In reply to comment #1)
> Subject: Re: New: [gomp] Trouble with threadprivate and extern
>
> On Thursday 20 October 2005 12:34, reichelt at gcc dot gnu dot org wrote:
>
> > I'd expect that i is threadprivate in
--- Comment #1 from dnovillo at redhat dot com 2005-10-20 16:45 ---
Subject: Re: New: [gomp] Trouble with threadprivate and extern
On Thursday 20 October 2005 12:34, reichelt at gcc dot gnu dot org wrote:
> I'd expect that i is threadprivate in file1.c and file2.c.
>
But you have to
