On 10/02/2015 15:23, John N1ISA wrote: > Hi Joe/Bill/Developers, Hi John, > > Last week, when I installed Bill's wsjtx_omp.patch, and ran the Linux command > top in a terminal, I would see the PID jt9_omp at the 50 second mark at > decode. OK. > > To keep this post short, and to the point, I recently built WSJTX with Ubuntu > 15.04 "Vivid" alpha 2. There are lot's of package updates that seem to me to > be very pertinent to building WSJTX in Linux. Even QT5 has been updated. > WSJTX builds, and functions perfectly in Ubuntu 15.04. WSJT-X has been tested with Qt up to version 5.4 which is the current release. > > Anyway, I've just installed Bill's r4950 Commit. I do not see jt9_omp anymore > when running the top command. You should if the patch to mainwindow.cpp is still in place, you may need to apply it again if you deleted your workspace rather than updating it. > > It is my understanding that when using a gcc compiler, that OpenMP is built > in. It depends how the compiler itself is built, but I would be surprised if a Linux distribution did not build their gcc tool suite without OpenMP support. You can check as follows:
$ gcc -fopenmp -dM -E - </dev/null | grep OPENMP #define _OPENMP 201107 That should list the _OPENMP define if the compiler supports OpenMP. The define above is what is returned on my Ubuntu 14.04 LTS system. If it doesn't WSJT-X will still work, it just won't decode JT65 and JT9 in parallel. > > Do I still need to apply Bill's patch? Does Commit r4950 turn on OpenMp in > WSJTX, except on non-Mac platforms? Or, is this just Bill's effort to setup > the future use of OpenMP at a later date? For now yes you do need the patch. At some point when it is agreed by all the OpenMP is worth using and it is working correctly on all platforms; jt9_omp will be discarded and jt9 will be built with OpenMP enabled, then the patch will no longer be needed. This point is very close as the Mac version is now building and working. It just remains for anyone comparing jt9 and jt9_omp performance to comment. Note that even when jt9 uses OpenMP there is still the option to limit its use of threads by defining the environment variable OMP_TREAD_LIMIT=1 which will cause jt9 to revert to sequential decoding. This will happen automatically on uni-processor systems since OpenMP is set to never use more threads than there are CPUs to service them. > > Am I running WSJTX correctly? Yes, as far as I can see. > > I would like to run WSJTX-devel, in a Linux environment, in such a way that > would expose any useful reportable bugs to the developers. That is appreciated. > > 73, John, N1ISA 73 Bill G4WJS. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
