[CSC 435] Parallel Quistions, Coding, and Debugging

[Andrew J. Pounds]

I'm already starting to get questions e-mailed to me regarding the
pthreads codes you are working on.  Remember, if you have a question
related to your code, please check your code into Anvil and open an
issue for me.   In most situations I will clone your repo, create a new
branch on which I make comments and/or corrections, and then push it
back to anvil as a merge request for you to complete.

Once you start writing parallel code you will most likely start to see a
lot of seg faults and errors related to pointers.  These are not easy to
track down -- but luckily, since we are working only on a single system
with a unified memory, you can still use lots of print statements in
your main program and threaded functions to help you track down the
errors.    In CUDA and MPI programming we generally don't have that
"luxury"....



-- 
Andrew J. Pounds, Ph.D.  (pounds_aj at mercer.edu)
Professor of Chemistry and Computer Science
Mercer University,  Macon, GA 31207   (478) 301-5627
http://faculty.mercer.edu/pounds_aj