To illustrate each of the addressing modes discussed in this chapter, translate the following pseudocode into MIPS assembly. The variables x and y should be placed in data memory because they are static and volatile. You do not need to keep the variables in memory while utilising register direct access. main() { static volatile int miles = prompt("Enter the number of miles driven: "); static volatile int gallons = prompt("Enter the number of gallons used: "); static volatile int mpg = miles / gallons; output("Your mpg = " + mpg); }

To illustrate each of the addressing modes discussed in this chapter, translate the following pseudocode into MIPS assembly. The variables x and y should be placed in data memory because they are static and volatile. You do not need to keep the variables in memory while utilising register direct access. main() { static volatile int miles = prompt("Enter the number of miles driven: "); static volatile int gallons = prompt("Enter the number of gallons used: "); static volatile int mpg = miles / gallons; output("Your mpg = " + mpg); }

Microsoft Visual C#

7th Edition

ISBN:9781337102100

Author:Joyce, Farrell.

Publisher:Joyce, Farrell.

Chapter8: Advanced Method Concepts

Section: Chapter Questions

Problem 7RQ

See similar textbooks

Similar questions

Translate the following pseudo code into MIPS assembly to show each of the addressing modes covered in this chapter. Note that variables x and y are static and volatile, so should be stored in data memory. When using register direct access, you do not need to store the variables in memory. main() { static volatile int miles = prompt("Enter the number of miles driven: "); static volatile int gallons = prompt("Enter the number of gallons used: "); static volatile int mpg = miles / gallons; output("Your mpg = " + mpg);}
MIPS Simulator QtSpim: You are to have a complete program in MIPS assembly language that behaves exactly as the included C program. This program contains four functions in addition to the main() one. Your solution must contain all five C routines as they have been coded in the example. Make sure to run the program in MIPS and show the same output on MIPS as well to make sure there are no errors. Below is the five C routines and attached is the image of what the output must print out on QtSpim. #include <stdio.h> int getMax(int arr[], int n){int mx = arr[0];for (int i = 1; i < n; i++)if (arr[i] > mx)mx = arr[i];return mx;}void countSort(int arr[], int n, int exp){int output[n];int i, count[10] = { 0 };for (i = 0; i < n; i++)count[(arr[i] / exp) % 10]++;for (i = 1; i < 10; i++)count[i] += count[i - 1];for (i = n - 1; i >= 0; i--) {output[count[(arr[i] / exp) % 10] - 1] = arr[i];count[(arr[i] / exp) % 10]--;}for (i = 0; i < n; i++)arr[i] = output[i];}void…
One of the special pointers is not like the others. The pointer is made up of call-saved registers, meaning extra precautions must be taken when using it.
*C PROGRAM FOR MICROPROCESSOR* Write a C program that will use 7-segement LEDS to display the number of key on the keypad when it is pressed. The display needs to stay on the 7-segment LEDS until the next key is pressed. Interrupt method is not required.
In simple words, describe the final data pointer register.
The addressing mode which makes use of in-direction pointers is А. Relative addressing mode В. Offset addressing mode C. Index addressing mode D. Indirect addressing mode
To illustrate each of the addressing modes discussed in this chapter, translate the following pseudocode into MIPS assembly. The variables x and y should be placed in data memory since they are static and volatile. There is no requirement to keep the data while utilising registration direct access. variables in memory.main() { static volatile int miles = prompt("Enter the number of miles driven: "); static volatile int gallons = prompt("Enter the number of gallons used: "); static volatile int mpg = miles / gallons; output("Your mpg = " + mpg);}
Draw a memory diagram for the following code
Assignment for Computer Architecture Instructions: The assignment is to create a program that adds the number 1/2 to itself a large number of times and adds the number 1/3 to itself a large number of times separately first using type float and then type double. It is to then compare the values of adding the numbers to multiplying 1/2 time the number of times added to compute the “same sum” in a different way. The program will also multiply 1/3 times the number of times 1/3 was added to itself to compute the “same sum” in a different way. The program will then compare these two methods at arrive for the same value and output the difference. Hint, the value for the ½’s will be the same for the smaller numbers of times, the 1/3’s will never be the same. The output from your program is to be to a *.txt file which you are to turn in along with your code. The program must first add the ½’s and 1/3’s using type float and compare to the value obtain using multiplication instead of addition.…
Patti the Programmer loads the EBX register with a pointer value as shown below: static: iValue: int16 := 0; begin progExample; mov(&iValue, EBX); // Patti uses [EBX] end progExample; After she has finished using EBX, must Patti the Programmer FREE EBX? Non of the choices listed are correct No Yes The answer will depend on the value of iValue
To demonstrate each of the addressing modes presented in this chapter, translate the following pseudo code into MIPS assembly. Because variables x and y are static and volatile, they should be kept in data memory. You do not need to save the register while utilising registration direct access. variables in memory.main() { static volatile int miles = prompt("Enter the number of miles driven: "); static volatile int gallons = prompt("Enter the number of gallons used: "); static volatile int mpg = miles / gallons; output("Your mpg = " + mpg);}
Translate the following pseudo code into MIPS assembly to show each of the addressing modes.. Variables x and y should be maintained in data memory since they are static and volatile. When using register direct access, you do not need to retain variables in memory. main() { static volatile int miles = prompt("Enter the number of miles driven: "); static volatile int gallons = prompt("Enter the number of gallons used: "); static volatile int mpg = miles / gallons; output("Your mpg = " + mpg); }