1,885
edits
Changes
→Topics
{|class="wikimedia sortable" border="1" cellpadding="5" cellspacing="0"
!Topic!!Question/Topic Description!!Student!!Links to resources (Wiki page, handout, web resources)
|-
|x86 Registers||What are the names and sizes of all of the x86_64 registers? Why are they named this way? Which ones have special significance, unusual operation, or are required for specific operations?|| Kieran Sedgwick||
|-
|Aarch64 Registers||What are the names and sizes of all of the Aarch64 registers? Why are they named this way? Which ones have special significance, unusual operation, or are required for specific operations?|| Edwin Lum||
|-
|Absolute addressing and Immediate values on Aarch64||In Aarch64 systems, the size of each instruction is limited to 64 bits. Since some bits are required to encode the operation, addressing mode, and registers, the number of bits available to specify an address or immediate value (constant) are limited. How are constant values represented, and what are the limitations on the values that can be included? How can you work around these limitations?|| ||
|-
|NASM Syntax||What is NASM, and what are the basic rules of NASM syntax? How do you use preprocessor directives (such as #include and #define) or equivalent?|| Omid Djahanpour||
|-
|GNU x86_64 gas Syntax||What are the basic rules of GNU Assembler (gas) syntax for x86_64 platforms? How do you use preprocessor directives (such as #include or #define) or equivalent?|| Brendan Henderson||
|-
|GNU aarch64 Syntax||What are the basic rules of GNU Assembler (gas) syntax for aarch64 platforms? How do you use preprocessor directives (such as #include or #define) or equivalent?|| ||
|-
|Argument storage on x86_64||When a function/procedure is called on an x86_64 Linux system, where are the arguments stored? What if there are many arguments?|| Adam Sharpe||
|-
|Argument storage on aarch64||When a function/procedure is called on an aarch64 Linux system, where are the arguments stored? What if there are many arguments?|| ||
|-
|System call numbers on x86_64||What are the system call numbers on an x86_64 Linux system? Where are they defined and how do you use them?|| ||
|-
|System call numbers on aarch64||What are the system call numbers on an aarch64 Linux system? Where are they defined and how do you use them?|| ||
|-
|PLT||In an ELF file, what is a PLT and how is it used? When does an ELF file not contain a PLT?|| ||
|-
|Assembling using gas||How do you use the GNU assembler (gas) to compile an assembly-language program ("assemble" it) from the command line, producing an executable file? What are some useful command-line options?|| ||
|-
|Single-stepping with gdb||How do you execute a program one instruction at a time (single-stepping) using the GNU debugger (gdb)? How do you view register contents between steps?|| Hunter Jansen||
|-
|Dividing integers on x86_64 and aarch64||How do the integer division instructions work on x86_64 and aarch64? How are they different? What are the advantages of each?|| Gabriel Castro||
|-
|Static and dynamic linking||What are the differences between static and dynamic linking? What are the advantages of each from the point of view of performance, resource utilization, and security?|| Linpei Fan||
|-
|The Mysterious XOR||x86 and x86_64 code often contains instructions that XOR a register with itself (e.g., <code>xor %eax,%eax</code>). What does this do and why is it used? What is the equivalent in Aarch64?|| Emmanuel Ho Fidelino||
|-
|}