Related topics

Assistance with threading ...thread not returning
3743 NullP sth/s perl 5.011000 i686-cygwin-thread-multi-64int (gcc 3.4.4 -O3) 0.000267s test.pl done [MSG] [Fri Feb 29 23:01:52 2008] Sending test report ..... Dubious, test returned 255 (wstat 65280, 0xff00) No subtests run Can't use string ("Data::ObjectDriver::Driver::DBD:") as a SCALAR ref while "strict refs"

FAIL Data-Queue-Persistent-0.11 darwin-thread-multi-64int-2level ...
27777 NullP sth/s perl 5.008008 x86_64-linux-thread-multi-ld (gcc 4.1.2 -g -O3) 0.000036s test.pl done [MSG] [Thu Feb 28 14:35:56 2008] Sending test report for ccflags ='-D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include

using volatile bools instead of mutexes when synchronizing threads
16732 NullP sth/s perl 5.008008 i386-freebsd-thread-multi-64int (gcc 3.4.6 -O) 0.000060s test.pl done [MSG] [Fri Feb 8 20:31:21 2008] Ok, if you have aC compiler cc -c -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -O -DVERSION=\"0.21\"

FAIL Data-ObjectDriver-0.05 darwin-thread-multi-64int-2level 8.10.0
You should be able to disable it by using strict threading. View - Global Options - Display - "Organize articles ...." Select by ID only. Sometimes, if you do this you may see threads broken into subthreads arranged in a manner that is not what you expect. Thanks Tom. I'll give it a try. Looks OK so far.

FAIL Data-Queue-Persistent-0.11 x86_64-linux-thread-multi-ld 2.6.22.10
16623 NullP sth/s perl 5.008008 i386-freebsd-thread-multi-64int (gcc 3.4.6 -O) 0.000060s test.pl done [MSG] [Mon Feb 25 21:51:33 2008] Ok, not sending test .... optimize='-O', cppflags='-DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include' ccversion='',

Threading crash with closures
Look back at my notes on "strict C++", and what people griped about then. John Nagle Animats Francis Glassborow wrote: In article <408d9767$0$436$afc38...@news.optusnet.com.au>, Thorsten Ottosen <neso...@cs.auc.dk> writes "John Nagle" <na...@animats.com> wrote in message

Threading with non-shared libraries
This seems to take a too traditional and too strict view. Your emphasis above is on compiler, but that operative word is a slippery one. This program might have no observable behaviour at all, but you can still force the order of execution generated by the *compiler* by hiding the definition of func1, func2 without

Scott & Andrei article on DCLP and threading... Flawed ?
For some reason, as far as concurrent IO is concerned people often think of threading as the only possible solution for this kind of problem. The solution was to assure that locks are ALWAYS acquired in a strict order, which is HARD to verify if they're acquired by different functions and the calling-caller map

Groovy performance: what to do
11904 NullP sth/s perl 5.008008 i686-linux-thread-multi-64int-ld (gcc 4.1.2 -O2) 0.000084s test.pl done [MSG] [Sun Feb 10 15:43:23 2008] Sending test report for cc -c -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -D_LARGEFILE_SOURCE

FAIL DashProfiler-1.09 i686-linux-thread-multi-64int-ld 2.6.21.5-smp
Looks good I see you're using perl 5.010000 on i686-linux-thread-multi-64int-ld, okay. Remember to actually *read* the README file! ...... as a SCALAR ref while "strict refs" in use at /home/cpan/perl5.10.00/.cpanplus/5.10. 0/build/Data-ObjectDriver-0.05/blib/lib/Data/ObjectDriver/Driver/DBD.pm line 13.

The choice of threading primitives
And if strict threading is made mandatory, I see no reason for crossposting anything but pointers. Those interested can read the discussion here, and those who are not interested can avoid the debate if they so wish. But without strict threading, I fear a lot of people won't go near news.groups since they have to

FAIL Data-Queue-Persistent-0.10 i686-cygwin-thread-multi-64int 1.5 ...
45454 NullP sth/s perl 5.011000 x86_64-linux-thread-multi-ld (gcc 4.2.3 -O2) 0.000022s test.pl done [MSG] [Sat Feb 23 10:21:50 2008] Sending test report for .... cppflags='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing

Summer '77
4376 NullP sth/s perl 5.010000 darwin-thread-multi-64int-2level (gcc 4.0.1 -O3) 0.000229s test.pl done [MSG] [Wed Feb 27 07:14:55 2008] Sending test report ..... uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -pipe

(Gravity) Future Support?
... I had to do this was to pass a reference of the form to the Class Invader and Gun, this way I could do the Invoke of the method on the UI Thread in the form. While some may discourage using global variables, and avoid them at all costs, I am not that strict. It pays off, on occasion, to make a few objects

FAIL EekBoek-1.03.10 i386-pc-solaris2.11-thread-multi-64int 2.11
An exception will be thrown when the mutex is not held by this thread, so mistakes in using a wrong mutex should be detected (except when the other mutex is locked too, I'm here breaking strict ISO/ANSI C rules: the signal handler modifies global volatile variables of pointer type, not just sig_atomic_t.

FAIL Data-Queue-Persistent-0.10 x86_64-linux-thread-multi-ld 2.6.22.10
... Claus Guttesen wrote: We just had our first lockup for today - and the last one. Next step is to downgrade to Linux :( *crud* /etc/make.conf: CPUTYPE=i686 CFLAGS= -O2 -pipe -funroll-loops -fno-strict-aliasing COPTFLAGS= -O2 -pipe -funroll-loops man make.conf Now read the descriptions for CFLAGS and COPTFLAGS.

Linux 64Bit
Please also email dbi-...@perl.org and include the output of 'perl -V' *** You are using a perl configured with threading enabled. 2008] cc -c -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -fno-strict-aliasing -pipe -Wdeclaration-after-statement -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64

FAIL ObjectDBI-0.11 OpenBSD.i386-openbsd-thread-multi 4.1
8264 NullP sth/s perl 5.010000 i386-netbsd-thread-multi-64int (gcc 3.3.3 -O) 0.000121s test.pl done [MSG] [Mon Feb 25 18:57:44 2008] Sending test report for ..... ccflags ='-fno-strict-aliasing -pipe -I/usr/pkg/include', optimize='-O', cppflags='-fno-strict-aliasing -pipe -I/usr/pkg/include' ccversion='',

Threading issue in next standard
10638 NullP sth/s perl 5.010000 i686-linux-thread-multi-64int-ld (gcc 4.1.2 -O2) 0.000094s test.pl done [MSG] [Tue Feb 26 21:01:55 2008] Sending test report for .... cppflags='-D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -I/usr/local/include' ccversion='', gccversion='4.1.2', gccosandvers='' intsize=4,

FAIL Data-ObjectDriver-0.05 i686-cygwin-thread-multi-64int 1.5.24 ...
8230 NullP sth/s perl 5.008008 OpenBSD.i386-openbsd-thread-multi (gcc 3.3.5 -O2) 0.000122s test.pl done [MSG] [Sat Feb 23 06:08:37 2008] Ok, ..... bincompat5005=undef Compiler: cc='cc', ccflags ='-pthread -fno-strict-aliasing -fno-delete-null-pointer-checks -pipe -I/usr/local/include', optimize='-O2',