Difference between revisions of "Fall 2014 SPO600 Assembly Language Presentation"
Chris Tyler (talk | contribs) (→Assignment) |
Chris Tyler (talk | contribs) (→Topics) |
||
| Line 12: | Line 12: | ||
!Topic!!Question/Topic Description!!Student | !Topic!!Question/Topic Description!!Student | ||
|- | |- | ||
| − | |x86 Registers||What are the names and sizes of all of the x86_64 registers?|| | + | |x86 Registers||What are the names and sizes of all of the x86_64 registers? Which ones have special significance, unusual operation, or are required for specific operations?|| |
|- | |- | ||
| − | |Aarch64 Registers||What are the names and sizes of all of the Aarch64 registers?|| | + | |Aarch64 Registers||What are the names and sizes of all of the Aarch64 registers? Which ones have special significance, unusual operation, or are required for specific operations?|| |
|- | |- | ||
| − | | | + | |Absolute addressing and Immediate values on Aarch64||In Aarch64 systems, the total 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. What are the limitations? 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?|| |
|- | |- | ||
| − | |GNU | + | |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?|| |
|- | |- | ||
| − | | | + | |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 | + | |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?|| |
|- | |- | ||
| − | | | + | |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 | + | |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?|| |
|- | |- | ||
| − | | | + | |Static and dynamic linking||What are the differences between static and dynamic linking? Advantages of each from the point of view of performance, resource utilization, and security?|| |
|- | |- | ||
| − | |Assembling using gas||How do you use the GNU assembler (gas) to compile an assembly-language program ("assemble" it)?|| | + | |Assembling using gas||How do you use the GNU assembler (gas) to compile an assembly-language program ("assemble" it) from the command line?|| |
|- | |- | ||
| − | |Single-stepping with gdb||How do you execute a program one instruction at a time (single-stepping) using the GNU debugger (gdb)?|| | + | |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?|| |
|- | |- | ||
| − | |Dividing on x86_64 and aarch64||How do the division instructions work on x86_64 and aarch64? How are they different?|| | + | |Dividing integers on x86_64 and aarch64||How do the division instructions work on x86_64 and aarch64? How are they different? What are the advantages of each?|| |
|- | |- | ||
| − | |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?|| | + | |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?|| |
|- | |- | ||
|} | |} | ||
Revision as of 14:12, 10 September 2014
Assignment
- Select one of the topics below by placing your name in the "Student" column (first come, first served).
- During week 3, research the topic and prepare a 3- to 5-minute presentation to teach the answer to the class.
- Be prepared to teach this presentation during week 4. You may want to draw whiteboard diagrams, use presentation slides, or have a 1-page handout. Please do not exceed 5 minutes in total for your presentation.
Topics
| Topic | Question/Topic Description | Student |
|---|---|---|
| x86 Registers | What are the names and sizes of all of the x86_64 registers? Which ones have special significance, unusual operation, or are required for specific operations? | |
| Aarch64 Registers | What are the names and sizes of all of the Aarch64 registers? Which ones have special significance, unusual operation, or are required for specific operations? | |
| Absolute addressing and Immediate values on Aarch64 | In Aarch64 systems, the total 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. What are the limitations? 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? | |
| 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? | |
| 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? | |
| 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? | |
| Static and dynamic linking | What are the differences between static and dynamic linking? Advantages of each from the point of view of performance, resource utilization, and security? | |
| Assembling using gas | How do you use the GNU assembler (gas) to compile an assembly-language program ("assemble" it) from the command line? | |
| 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? | |
| Dividing integers on x86_64 and aarch64 | How do the division instructions work on x86_64 and aarch64? How are they different? What are the advantages of each? | |
| The Mysterious XOR | x86 and x86_64 code often contains instructions that XOR a register with itself (e.g., xor %eax,%eax). What does this do and why is it used? What is the equivalent in Aarch64? |
