//inheritance protected member
#include <iostream.h>
#include <conio.h>
class parent
{
protected:
int no;
char str[10];
};
class child : protected parent
{
public:
void getdata()
{
cout << endl << "Enter any string : ";
cin.getline(str, 10);
cout << "Enter any number : " ;
cin >>no;
}
void display()
{
cout << endl << "Number is " << no;
cout << endl << "String is " << str;
}
};
void main()
{
clrscr();
child obj;
obj.getdata();
obj.display();
getch();
}
Quetion 6 : Consider the "in-order-issue/in-order-completion" execution sequence shown in f In Figure Decode OWE Execute 12 12 12 14 16 13 16 13 15 15 16 Write 024/06/02 11 3 4 11 12 13 13 N 15 16 a. Identify the most likely reason why I could not enter the execute fourth cycle. stage until the [2] b. Will "in-order issue/out-of-order completion" or "out-of-order issue/out-of-order completion" fix this? If so, which? Explain
Answer: a. Identify the most likely reason why I could not enter the execute stage until the fourth cycle. One likely reason an instruction couldn't enter the execute stage until the fourth cycle is due to data hazards or resource conflicts: 1. Data Hazards: If the instruction depends on the result of a previous instruction that hasn't completed yet, it cannot proceed to the execute stage. This is often referred to as a Read After Write (RAW) hazard. 2. Resource Conflicts: If the required functional unit for execution (e.g., an ALU) is occupied by another instruction, the instruction will have to wait until the resource becomes available. b. Will "in-order issue/out-of-order completion" or "out-of-order issue/out-of-order completion" fix this? If so, which? Explain In-order issue/out-of-order completion might help if the problem is related to instructions that can complete earlier being delayed by instructions that take longer to execute. This allows the...
Comments
Post a Comment