[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-27 Thread edwintorok at gmail dot com
--- Comment #20 from edwintorok at gmail dot com 2010-01-27 12:35 --- Thanks to Jakub for the hints. This is not a bug in libstdc++/gcc: the problem is that fork() is called when we already have threads (due to openmp/libstdc++ parallel mode), and then you can call a limited number of

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-15 Thread paolo dot carlini at oracle dot com
--- Comment #19 from paolo dot carlini at oracle dot com 2010-01-15 14:35 --- Let's add Jakub in CC, he knows the implementation very well. In case, please keep also in touch privately. -- paolo dot carlini at oracle dot com changed: What|Removed

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-15 Thread singler at kit dot edu
--- Comment #18 from singler at kit dot edu 2010-01-15 14:30 --- Created an attachment (id=19617) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19617&action=view) Add printf debug statements. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42624

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-15 Thread singler at kit dot edu
--- Comment #17 from singler at kit dot edu 2010-01-15 14:30 --- Created an attachment (id=19616) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19616&action=view) Removes superfluous pragma omp single twice -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42624

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-15 Thread singler at kit dot edu
--- Comment #16 from singler at kit dot edu 2010-01-15 14:29 --- First, let's remove superfluous #pragma omp single in two occurences, to make things simpler (see attached patch for trunk). The problem still persists, the program deadlocks. When dropping in some prints (see attached pat

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-13 Thread edwintorok at gmail dot com
--- Comment #15 from edwintorok at gmail dot com 2010-01-13 20:39 --- (In reply to comment #14) > (In reply to comment #13) > > > This code is compiled with -fno-exceptions, could that be a problem? > > No, that should rather help. > > Still, it is very difficult to debug this. Is th

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-13 Thread singler at kit dot edu
--- Comment #14 from singler at kit dot edu 2010-01-13 13:53 --- (In reply to comment #13) > This code is compiled with -fno-exceptions, could that be a problem? No, that should rather help. Still, it is very difficult to debug this. Is there at least a way to access clamd's stdout a

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread edwintorok at gmail dot com
--- Comment #13 from edwintorok at gmail dot com 2010-01-12 17:54 --- (In reply to comment #12) > Thread 1 waits for its colleagues, but where are they gone? Is it possible > that an exception is thrown inside find (by means of the value type or the > predicate)? > I don't fully trust g

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread singler at kit dot edu
--- Comment #12 from singler at kit dot edu 2010-01-12 17:42 --- Thread 1 waits for its colleagues, but where are they gone? Is it possible that an exception is thrown inside find (by means of the value type or the predicate)? I don't fully trust gdb in this case, but it shows that an i

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread singler at kit dot edu
--- Comment #11 from singler at kit dot edu 2010-01-12 14:35 --- (In reply to comment #9) > Could this bug be related to this one: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36242#c4 This bug is invalid for GCC 4.4. > Clamd creates threads using pthread_create, std::find is called f

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread singler at kit dot edu
--- Comment #10 from singler at kit dot edu 2010-01-12 14:35 --- Can reproduce deadlock now. -- singler at kit dot edu changed: What|Removed |Added AssignedTo|una

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread edwintorok at gmail dot com
--- Comment #9 from edwintorok at gmail dot com 2010-01-12 13:35 --- Could this bug be related to this one: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36242#c4 Clamd creates threads using pthread_create, std::find is called from those threads. There are also threads that only poll/disp

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread edwintorok at gmail dot com
--- Comment #8 from edwintorok at gmail dot com 2010-01-12 12:51 --- (In reply to comment #7) > > What happens for OMP_NUM_THREADS=1? > > Will test now. It doesn't hang with OMP_NUM_THREADS=1. It does hang with OMP_NUM_THREADS=2, or with OMP_NUM_THREADS unset. > > Please enter the GCC

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread edwintorok at gmail dot com
--- Comment #7 from edwintorok at gmail dot com 2010-01-12 12:41 --- (In reply to comment #6) > Can I get this thing to run without actually installing it into the system? > > 5. clamd/clamd -c etc/clamd.conf > LibClamAV Error: cl_load(): Can't get status of /usr/local/share/clamav > ER

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread singler at kit dot edu
--- Comment #6 from singler at kit dot edu 2010-01-12 12:36 --- Can I get this thing to run without actually installing it into the system? 5. clamd/clamd -c etc/clamd.conf LibClamAV Error: cl_load(): Can't get status of /usr/local/share/clamav ERROR: Can't get file status Please enter

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-12 Thread paolo dot carlini at oracle dot com
--- Comment #5 from paolo dot carlini at oracle dot com 2010-01-12 11:54 --- Thanks. If you could do your best to figure out something small and self contained it would be great, otherwise we lack anyway something to add to the testsuite. -- http://gcc.gnu.org/bugzilla/show_bug.cgi

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-11 Thread edwintorok at gmail dot com
--- Comment #4 from edwintorok at gmail dot com 2010-01-12 07:28 --- (In reply to comment #3) > Johannes is looking into it, Thanks. > certainly reproducing the problem will not be a > trivial taks, I'm afraid... > If the steps I listed in the bugreport don't work for you just let me

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-11 Thread paolo dot carlini at oracle dot com
--- Comment #3 from paolo dot carlini at oracle dot com 2010-01-12 02:19 --- Johannes is looking into it, certainly reproducing the problem will not be a trivial taks, I'm afraid... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42624

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-05 Thread paolo dot carlini at oracle dot com
--- Comment #2 from paolo dot carlini at oracle dot com 2010-01-05 19:22 --- The best we can do is asking the attention of Johannes... -- paolo dot carlini at oracle dot com changed: What|Removed |Added

[Bug libstdc++/42624] libstdc++ parallel mode deadlocks in barrier

2010-01-05 Thread edwintorok at gmail dot com
--- Comment #1 from edwintorok at gmail dot com 2010-01-05 18:09 --- (In reply to comment #0) > $ make -j4 This should have been: make CCLD=g++ -j4 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42624