------- Comment #45 from iains at gcc dot gnu dot org  2010-06-02 19:15 -------
(In reply to comment #44)
> This seems linked to the optimization:
> 
> [macbook] f90/bug% /opt/gcc/build_w/prev-gcc/xgcc -B/opt/gcc/build_w/prev-gcc/
> -O2 -pthread pthread_create.c -o tls.ex
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        9
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        7
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>       26
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>      420
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>      266
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>      277
> [macbook] f90/bug% /opt/gcc/build_w/prev-gcc/xgcc -B/opt/gcc/build_w/prev-gcc/
> -O1 -pthread pthread_create.c -o tls.ex
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>       11
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        9
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>       10
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>      357
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>      391
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>      376
> [macbook] f90/bug% /opt/gcc/build_w/prev-gcc/xgcc -B/opt/gcc/build_w/prev-gcc/
> -pthread pthread_create.c -o tls.ex
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        0
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        1
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        0
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        1
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        0
> [macbook] f90/bug% rm -f tmp ; tls_1.sh > tmp ; cat tmp | wc -l
>        0
> 
> For each O level, the first 3 runs are for an idle system and the 3 others for
> a loaded one.

hm.  that might be bad news :-( 

I've got a patch that puts some TLS tests into the torture tests  - I'll dig
them out and see what happens on current trunk.

It's odd that this is only affecting x86_64-d10 tho, if it's an error of that
nature....

1) have you got my 'proper' TLS patch to hand? (attached to PR44132).
2) do you have time to rebootstrap w that patch ?
3) what compiler do you use for stage1? 

(I saw in the related PR about 4.5.0 that the TLS stuff was looking enabled at
stage1 - which is odd if the apple compiler is being used, since it doesn't
have tls ;))


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43170

Reply via email to