Changes

Jump to: navigation, search

Winter 2022 SPO600 Project

494 bytes added, 20:03, 13 April 2022
Stage 3: Upstreaming
'''Due: Monday, April 18, 11:59 pm''' (Revised)
== Stage 3: <s>Upstreaming </s> Analysis ==
<s>
# Get your changes into the upstream codebase, if applicable.
## A disassembly of the SVE2 code in your solution (regardless of whether it's there through autovectorization, inline assembly, or the use of the ACLE intrinsics). Explain in detail how the code works. (If you have used the autovectorizer, choose one or two places where SVE2 code was generated - you don't have to cover all of them).
## Explain how you think the SVE2 code will perform compared to the original code, and why.
## Show that the final version of the program works as well as the original version (e.g., process the same data file with both programs and compare the output, or otherwise test the operation of the program. Make sure that the SVE2 code gets used!).
## Any other analysis that you think is useful. For example, you could choose some combination of these:
##* Show that your changes don't break the build or cause improper or slower operation on other platforms (like x86_64).
##* Discuss how a version of the software could be built that would choose at runtime whether to use SVE2 instructions (if available) or not (if unavailable).
##* Recommend the next steps that could/should be taken to continue your work (for example, other functions/methods that should be optimized for SVE2).
 
 
If you were not successful in getting your selected program to build with SVE2 code:
# Explain why. Be detailed in your explaination, and include appropriate details including compiler output or other supporting evidence.
# Explain in detail how this could be remedied, or why it doesn't make sense. Analyze the potential benefits or disadvantages of adding SVE2 code to the program.
# Add any other analysis you think would be useful.
# Reflect on the process of doing this project, what parts (if any!) were interesting, and what skills or knowledge (if any!) you think you might be able to use in the future.
 
'''Due: Friday, April 22, 11:59 pm (firm)'''

Navigation menu