Difference between revisions of "SPO600 Inline Assembler Lab"
Shivgajiwala (talk | contribs) (→Part B - Individual Task) |
(→Part B - Individual Task) |
||
Line 28: | Line 28: | ||
1. Select one of the following open source packages which is not claimed by another person in the class. Put your name beside it in (parenthesis) to claim it. | 1. Select one of the following open source packages which is not claimed by another person in the class. Put your name beside it in (parenthesis) to claim it. | ||
* amule (Lawrence) | * amule (Lawrence) | ||
− | * ardour | + | * ardour (Ray Gervais) |
* avidemux(Shiv Gajiwala) | * avidemux(Shiv Gajiwala) | ||
* blender | * blender |
Revision as of 15:53, 15 March 2017
Lab 7
References
Part A - Class Lab
1. Write a version of the Volume Scaling solution from the Algorithm Selection Lab for AArch64 that uses the SQDMULH or SQRDMULH instructions via inline assembler.
2. Test the performance of your solution and compare it to your previous solution(s).
3. Blog about your results in detail, including your reflections.
Part B - Individual Task
1. Select one of the following open source packages which is not claimed by another person in the class. Put your name beside it in (parenthesis) to claim it.
- amule (Lawrence)
- ardour (Ray Gervais)
- avidemux(Shiv Gajiwala)
- blender
- bunny (laily)
- busybox (laily)
- chicken
- cln (Len)
- coq
- cxxtools
- faad2
- fawkes
- gauche
- gmime
- gnash
- gridengine
- groonga
- hoard
- iaxclient
- k9copy
- lame
- libfame
- libgcroots
- libmad
- libmlx4
- lightsparc
- mediatomb
- mjpegtools
- mlt
- mosh
- mpich2
- ocaml-zarith
- openblas(Andrey)
- opencore-amr
- openser
- par2cmdline (Dang)
- picprog
- qlandkartegt
- sooperlooper (Quang)
- traverso
2. Find the assembler in that software, and determine:
- How much assembley-language code is present
- Which platform(s) it is used on
- Why it is there (what it does)
- What happens on other platforms
- Your opinion of the value of the assembler code VS the loss of portability/increase in complexity of the code.
3. Blog your results in detail.