[Bug libgomp/28468] OpenMP-parallelized program crashes when OMP_NUM_THREADS 1

2008-03-10 Thread jakub at gcc dot gnu dot org 


--- Comment #7 from jakub at gcc dot gnu dot org  2008-03-10 16:09 ---
No plaans to backport this to 4.2 anymore.


-- 

jakub at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||FIXED


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

[Bug libgomp/28468] OpenMP-parallelized program crashes when OMP_NUM_THREADS 1

2007-02-07 Thread jakub at gcc dot gnu dot org 


--- Comment #4 from jakub at gcc dot gnu dot org  2007-02-07 13:35 ---
Subject: Bug 28468

Author: jakub
Date: Wed Feb  7 13:35:17 2007
New Revision: 121689

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=121689
Log:
2007-02-07  Bruno Haible  [EMAIL PROTECTED]

config/
PR libgomp/28468
* config/tls.m4 (GCC_CHECK_TLS): Also check whether the libc supports
TLS via __thread.

2007-02-07  Jakub Jelinek  [EMAIL PROTECTED]

{libgomp,libstdc++-v3,libmudflap,libjava}/
PR libgomp/28468
* configure: Regenerate.

Modified:
trunk/config/ChangeLog
trunk/config/tls.m4
trunk/libgomp/ChangeLog
trunk/libgomp/configure
trunk/libjava/ChangeLog
trunk/libjava/configure
trunk/libmudflap/ChangeLog
trunk/libmudflap/configure
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/configure


-- 


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

[Bug libgomp/28468] OpenMP-parallelized program crashes when OMP_NUM_THREADS 1

2007-02-07 Thread jakub at gcc dot gnu dot org 


--- Comment #5 from jakub at gcc dot gnu dot org  2007-02-07 13:39 ---
Approved offline by Alex Oliva, committed so far on the trunk.
Will backport to 4.2 branch after a week or so on the trunk.


-- 


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

[Bug libgomp/28468] OpenMP-parallelized program crashes when OMP_NUM_THREADS 1

2006-11-15 Thread jakub at gcc dot gnu dot org 


--- Comment #2 from jakub at gcc dot gnu dot org  2006-11-15 09:45 ---
Was LinuxThreads built at least --with-tls support or without?
If without and libgomp has been built without --disable-tls and your
assembler/linker support TLS, libgomp might be using __thread eventhough
glibc doesn't support that.
There have been some patches added recently to improve gcc configure checks
for the runtime support of TLS.


-- 

jakub at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING


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

[Bug libgomp/28468] OpenMP-parallelized program crashes when OMP_NUM_THREADS 1

2006-11-15 Thread bruno at clisp dot org 


--- Comment #3 from bruno at clisp dot org  2006-11-15 13:38 ---
 Was LinuxThreads built at least --with-tls support or without?

The glibc was built with LinuxThreads without TLS. (I gave --without-tls
explicitly to the glibc build.)

 If without and libgomp has been built without --disable-tls and your
 assembler/linker support TLS, libgomp might be using __thread eventhough
 glibc doesn't support that.

Yes, this is exactly the problem; see the analysis and patch in
http://gcc.gnu.org/ml/gcc/2006-11/msg00244.html

 There have been some patches added recently to improve gcc configure checks
 for the runtime support of TLS.

The only patch that has been committed is this one from Daniel Jacobowitz
http://gcc.gnu.org/viewcvs/trunk/config/tls.m4?r1=117049r2=118777
It has no effect on this bug, since it applies only to the cross-compiling
case.

For the native compile, I posted a patch that is known to fix this bug:
http://gcc.gnu.org/ml/gcc/2006-11/msg00244.html
It has been approved by Richard Henderson:
http://gcc.gnu.org/ml/gcc/2006-11/msg00255.html
But noone has committed it to the GCC SVN.

Could someone please commit this patch on the HEAD and possibly on the 4.2
branch? (It is not a regression, if you argue that libgomp and -fopenmp is a
new feature. But it is a regression if you argue that there are packages out
there, such as GNU gettext 0.16, which use -fopenmp if available, and this
bug turns a program that would run unparallelized but correctly with gcc-4.1
into a program that runs parallelized but crashes with gcc-4.2.)


-- 

bruno at clisp dot org changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu dot org
 Status|WAITING |UNCONFIRMED


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

[Bug libgomp/28468] OpenMP-parallelized program crashes when OMP_NUM_THREADS 1

2006-11-07 Thread bruno at clisp dot org 


--- Comment #1 from bruno at clisp dot org  2006-11-07 14:36 ---
It's still reproducible with gcc-4.2-20061031:

$ export OMP_NUM_THREADS=2
$ gdb a.out 
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB.  Type show warranty for details.
This GDB was configured as i686-pc-linux-gnu...Using host libthread_db
library /lib/libthread_db.so.1.

(gdb) run
Starting program: /dev/shm/a.out 
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 4983)]
[New Thread 32769 (LWP 4984)]
[New Thread 16386 (LWP 4985)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16386 (LWP 4985)]
gomp_iter_dynamic_next (pstart=0xbf7ffa94, pend=0xbf7ffa98) at
../../../gcc-4.2-20061031/libgomp/iter.c:189
189   start = ws-next;
(gdb) where
#0  gomp_iter_dynamic_next (pstart=0xbf7ffa94, pend=0xbf7ffa98) at
../../../gcc-4.2-20061031/libgomp/iter.c:189
#1  0x4001ca78 in gomp_loop_dynamic_next (istart=0xbf7ffa94, iend=0xbf7ffa98)
at ../../../gcc-4.2-20061031/libgomp/loop.c:248
#2  0x080486ed in main.omp_fn.0 ()
#3  0x4001de5d in gomp_thread_start (xdata=0xbfffe580) at
../../../gcc-4.2-20061031/libgomp/team.c:108
#4  0x4003bfe6 in pthread_start_thread (arg=0xbf7ffbe0) at manager.c:310
#5  0x4003c07f in pthread_start_thread_event (arg=0xbf7ffbe0) at manager.c:334
#6  0x4014e0aa in clone () from /lib/libc.so.6


-- 


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