108
edits
Changes
→Progress
== Group Members ==
#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.('''He dropped the course.''')
== Progress ==
'''Nov 6th - 13th:'''
*There are great resources about Intel Parallel Debugger Extension for Microsoft Visual Studio like below.
# Debugging Threads in Intel Parallel Studio - [[http://www.drdobbs.com/windows/intel-parallel-debugger-extension-for-mi/214502747 Dr . Dobbs Article]]
# Intel® Parallel Debugger Extension, Added Aug 2, 2012 - [[https://software.intel.com/en-us/articles/parallel-debugger-extension]]
# Intel Parallel Composer Parallel Debugger Extension Tutorial - [[https://www.youtube.com/watch?v=uo3kAhVQUcs Mittie Sylvian's Video]]
However, Intel Parallel Debugger Extension has been deprecated from the version Intel Composer XE 2013at the end of 2012. I have noticed this from the Intel User Forum.*Intel Parallel Debugger Extension has been deprecated beginning with Intel(R) Composer XE 2013 at the end of 2012**[https://software.intel.com/en-us/forums/debug-solutions/topic/515990 Intel Parallel Debugger Extension has been deprecated?]
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 18th 14th - 23th17th:'''
*Links about Debug Multithreaded Applications in Visual Studio
#[https://msdn.microsoft.com/en-us/library/hh418499.aspx How to: Use the Parallel Watch Window]
#[https://msdn.microsoft.com/en-us/library/dd998398.aspx Using the Parallel Stacks Window]
<table>
<tr><td colspan="3">[[File:Parallel_stack_view.png|500px|thumb|left|Threads View from MSDN]]</td></tr><tr><td>Callout Letter</td><td>Element Name</td><td>Description</td></tr>
<tr><td>A</td><td>Call Stack Segment or Node</td><td>Contains a series of method contexts for one or more threads. </td></tr>
<tr><td>B</td><td>Blue Highlight</td><td>Presente Present the call path of the current thread.</td></tr>
<tr><td>C</td><td>Arrow lines</td><td>Connect nodes to make up the entire call path for the thread(s).</td></tr>
<tr><td>D</td><td>Tooltip on Node Header</td><td>Shows the ID and user-defined name of each thread whose call path shares this node.</td></tr>
</table>
----'''Nov 18th - 23th:''' '''Sample code to use debugging'''*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]]</ptd><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.
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.
As you see the rest of the major steps indicated in the data flows diagram.
**Parallel Stacks
<table border="0" width="800">
<tr><td width="400">[[File:qsort_set1.png|350px|thumb|left|qsort_set1]]</td>
<td width="400">[[File:qsort_set2.png|400px|thumb|left|qsort_set2]]</td></tr>
<tr><td>Recursive calling parallel_qsort of spawning parallel_qsort in the first parallel_qsort function which main thread has responsible for</td>
<td>The moment right after a spawning thread works in second parallel_qsort calling which Main Thread had finished</td></tr>
#[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]