Difference between revisions of "SPO600 Inline Assembler Lab"

From CDOT Wiki
Jump to: navigation, search
Line 8: Line 8:
 
* [[Inline Assembly Language]]
 
* [[Inline Assembly Language]]
 
* ARM Cortex-A Series Programmer’s Guide for ARMv8-A: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0024a/ch05s01.html
 
* ARM Cortex-A Series Programmer’s Guide for ARMv8-A: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0024a/ch05s01.html
 +
  
 
=== Part A - Start in Class ===
 
=== Part A - Start in Class ===

Revision as of 19:36, 13 February 2017

Lab icon.png
Purpose of this Lab
This lab is designed to explore the use of inline assembler, and its use in open source software.

Lab 7

References


Part A - Start in Class

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

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
  • ardour
  • avidemux
  • blender
  • bunny
  • busybox
  • chicken
  • cln
  • 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
  • opencore-amr
  • openser
  • par2cmdline
  • picprog
  • qlandkartegt
  • sooperlooper
  • 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.