Difference between revisions of "SPO600 Inline Assembler Lab"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
| Line 1: | Line 1: | ||
[[Category:SPO600 Labs]] | [[Category:SPO600 Labs]] | ||
| − | |||
{{Admon/lab|Purpose of this Lab|This lab is designed to explore the use of inline assembler, and its use in open source software.}} | {{Admon/lab|Purpose of this Lab|This lab is designed to explore the use of inline assembler, and its use in open source software.}} | ||
Revision as of 09:22, 19 February 2016
Purpose of this Lab
This lab is designed to explore the use of inline assembler, and its use in open source software.
This lab is designed to explore the use of inline assembler, and its use in open source software.
Lab 7
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
- filezilla
- 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.
