Changes

#Eunju Han [mailto:ejhan4@myseneca.ca?subject=GPU621%20from%20CDOT%20Wiki] Research etcand Demo.#<nowiki>Lei(Eric) Zhang </nowiki> [mailto:lzhang216@myseneca.ca?subject=GPU621%20from%20CDOT%20Wiki] Research etc. (Dropped '''He dropped the course.''') Research etc.

While I studied this Intel Parallel Debugger Extension, I needed to learn more about Parallel Studio version. Links about Intel® Parallel Studio XE 2017 #[https://software.intel.com/en-us/intel-parallel-studio-xe link1 Intel® Parallel Studio XE 2017]#[http://www.adeptscience.co.uk/products/cpp/intel-parallel-studio-xe link2 Intel® Parallel Studio XE 2017]#[https://software.intel.com/en-us/articles/intel-parallel-studio-xe-release-notes link Intel® Parallel Studio XE Release Notes] ----'''Nov 14th - 23th17th:'''

<tr><td colspan="3">[[File:Parallel_stack_view.png|500px|thumb|left|alt textThreads View from MSDN]]</td></tr>

* Sample code can be downloaded from here [https://software.intel.com/en-us/node/522584 Intel(R) Cilk(TM) quick sort] The debugging example below is used for five odd numbers to be sorted. This is the easiest way to figured out how the threads work together with the simple data. <table border="0" width="800"><tr><td width="360" align="top">*How to start debugging The following sequence may guides you start to debug on the visual Studio. # put breakpoints where you want to take a look by hitting the key F9 in the line or left-click at the front of a line# Run the program in Debug mode by hitting the green button (or key F5)# Go to the menu Debug -> Windows to open the windows you need ( see the image on your right)# Choose the windows that you need (e.g. Memory, Threads, Parallel Stacks, Local or Auto and so on.)# Hit the function keys to run a program: ## F10 to run codes line by line (Step Over)## F11 to go into a subroutine (Step Into) ## Shit +F11 to get out of a subroutine (Step Out)## F9 to put/remove breakpoints in a line      </td><td width="440">To open windows you need for debugging on Visual Studio, You must run a program in debug mode first. Otherwise, there is no menu to open the windows.[[File:debug_windows.png|440px|thumb|left|Menu Debug > Windows on VS 2015]]</td></tr></table>*Sample code results **Data flow of parallel_qsort<table border="0" width="800"><tr align="left"><td>[[File:dataflow.png|220px|thumb|left|Quick sorting dataflow]]</td><td>Fist set of this quick sorting is that main thread worked for first half of all elements which starts *begin 9 to *end 1. The *mid value was 9 so it swapped *mid for *end. Since mid moved to end, the second half of all elements was the end to the end which only end value are to be sorted; the actual process will be skipped so no value is changed. Next set of this is that second element(its value 3) to the last element (its value 9). The *mid value was 9 and swapping it for the *end which was same as before.  For the set 4-1 step, two Threads are working for this; Worker3 and Worker2 for two level parallel_qsort function calling and two level spawning call to parallel_qsort; values are already sorted so there was no swapping.

<tr><td>[[File:qsort_set1.png|300px|thumb|left|alt qsort_set1]]</td><td>Recursive calling parallel_qsort of spawning parallel_qsort in the first parallel_qsort function which main thread has responible for</td></tr><tr><td>[[File:qsort_set2.png|300px|thumb|left|alt qsort_set2]]</td><td></td></tr><tr><td>[[File:qsort_set3.png|300px|thumb|left|alt qsort_set3]]</td><td></td></tr><tr><td>[[File:qsort_set4_1.png|300px|thumb|left|alt qsort_set4_1]]</td><td></td></tr><tr><td>[[File:qsort_set4_done.png|300px|thumb|left|alt qsort_set4_done]]</td><td></td></tr><tr><td rowspan="5">[[File:dataflow.png|250px|thumb|right|alt dataflow]]</td></tr>

----* Debugging Tips*Parallel Stacks# Hit F9 at the front of a line to put the breakpoints<table border="0" width="800"># Run the program in Debug mode first and then open the windows you need<tr><td width="400">[[File:qsort_set1.png|350px|thumb|left|qsort_set1]]</td># Open the windows like Memory, Threads, Parallel Stacks, and Local or Auto<td width="400">[[File:qsort_set2.png|400px|thumb|left|qsort_set2]]</td></tr># Hit F10 or F11 to run codes line by line<tr><td>Recursive calling parallel_qsort of spawning parallel_qsort in the first parallel_qsort function which main thread has responsible for</td># F9 to put or remove breakpoints<td>The moment right after a spawning thread works in second parallel_qsort calling which Main Thread had finished</td></tr>

Links about Intel® ----* Tip for Parallel Studio XE 2017program debuggingThe followings will be a great approach to improve your debugging experience.First of all, doing debugging yourself is the best, not just see the videos or friend's working how to do debugging.

#[https://softwareUnderstanding a program is important; using a serial program version, follow codes line by line to understand the program.intel(Parallel programming usually starts from a serial version.com/en-us/intel-parallel-studio-xe link1 Intel® Parallel Studio XE 2017])#[http://wwwUse the simple data for the first time to keep track of data flow in a memory and then increase data volume for the program.adeptscience.co# When you missed the step you want to take a look in run-time debug mode, it will be better to start from the beginning in debug mode as data situation have already changed, and threads invocation also has been passed.uk/products/cpp/intel-parallel-studio-xe link2 Intel® Parallel Studio XE 2017]#[https://softwareTo open windows you need for debugging on Visual Studio, You must run a program in debug mode first.intelOtherwise, there is no menu to open the windows.com/en-us/articles/intel-parallel-studio-xe-release-notes link Intel® Parallel Studio XE Release Notes]