--- Comment #6 from jakub at gcc dot gnu dot org 2008-11-13 21:12 ---
Fixed.
--
jakub at gcc dot gnu dot org changed:
What|Removed |Added
Status|NEW
--- Comment #5 from sje at gcc dot gnu dot org 2008-11-13 21:08 ---
Subject: Bug 37938
Author: sje
Date: Thu Nov 13 21:06:38 2008
New Revision: 141830
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141830
Log:
PR libgomp/37938
* config/linux/ia64/mutex.h: New.
A
--- Comment #4 from sje at cup dot hp dot com 2008-11-04 16:54 ---
I have submitted a patch at
http://gcc.gnu.org/ml/gcc-patches/2008-11/msg00125.html
and will check it in tomorrow. It should fix all the libgomp failures on IA64
Linux.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?
--
hjl dot tools at gmail dot com changed:
What|Removed |Added
CC||hjl dot tools at gmail dot
|
--- Comment #3 from jakub at gcc dot gnu dot org 2008-10-31 20:15 ---
Linux specific because for non-Linux it uses libpthread pthread_mutex_lock etc.
to do the locking, only on Linux (--enable-linux-futex) it uses __sync_*
builtins for mutex.h locking.
--
http://gcc.gnu.org/bugzilla
--- Comment #2 from sje at cup dot hp dot com 2008-10-31 20:03 ---
It looks like it is Linux specific in addition to being IA64 specific. I can
make the included test case fail on my Debian Linux box but not on my HP-UX
box. If I do not optimize (-O0) then it fails more often then if I
--- Comment #1 from jakub at gcc dot gnu dot org 2008-10-28 15:02 ---
BTW, using + reduction in the same loop (and with asm optimization barrier for
that variable) I see the reduction computed value always correct, so the loop
body is executed the correct number of times. That means in
