cpu

问题 i've recently learned about out-of-order execution CPUs in this link https://en.wikipedia.org/wiki/Out-of-order_execution There is something that i can't quite understand. Why aren't these kind of CPUs troublesome? I mean, if i have instructions executing out of order, even if they apply to different data, wont i be able to reach a situation where data is not updated according to the program order? I mean, if i have something like: x = 1; y = 2; x = x+y; print x; print y; what prevents the

问题 i've recently learned about out-of-order execution CPUs in this link https://en.wikipedia.org/wiki/Out-of-order_execution There is something that i can't quite understand. Why aren't these kind of CPUs troublesome? I mean, if i have instructions executing out of order, even if they apply to different data, wont i be able to reach a situation where data is not updated according to the program order? I mean, if i have something like: x = 1; y = 2; x = x+y; print x; print y; what prevents the

问题 I am setting up my InstallShield to install my package as 64 bit (into Program Files not Program Files x86) by. My processor is: Intel(R) Core(TM) i7-2600 CPU InstallShield => General Information => Summary Information Stream => Template Summary From Intel32;1033 to Intel64;1033 And it gives me the general error message: This installation package is not supported by this processor Then I set the value to: Amd64;1033 or x64;1033 And it magically work. But weird thing is, my processor is Intel,

问题 I am setting up my InstallShield to install my package as 64 bit (into Program Files not Program Files x86) by. My processor is: Intel(R) Core(TM) i7-2600 CPU InstallShield => General Information => Summary Information Stream => Template Summary From Intel32;1033 to Intel64;1033 And it gives me the general error message: This installation package is not supported by this processor Then I set the value to: Amd64;1033 or x64;1033 And it magically work. But weird thing is, my processor is Intel,

问题 My question is how they co-exist and work together in modern CPU architecture? 回答1: You've got it slightly reversed. On every fetch you index into your branch predictor, which tells you whether the instruction that you have just received will be decoded into a taken branch. If not, you fetch the next sequential address. But if your branch predictor says that it will be a taken branch, you don't know which instruction to fetch next, since you haven't decoded this instruction yet. So in order

问题 My question is how they co-exist and work together in modern CPU architecture? 回答1: You've got it slightly reversed. On every fetch you index into your branch predictor, which tells you whether the instruction that you have just received will be decoded into a taken branch. If not, you fetch the next sequential address. But if your branch predictor says that it will be a taken branch, you don't know which instruction to fetch next, since you haven't decoded this instruction yet. So in order

问题 My question is how they co-exist and work together in modern CPU architecture? 回答1: You've got it slightly reversed. On every fetch you index into your branch predictor, which tells you whether the instruction that you have just received will be decoded into a taken branch. If not, you fetch the next sequential address. But if your branch predictor says that it will be a taken branch, you don't know which instruction to fetch next, since you haven't decoded this instruction yet. So in order

问题 My question is how they co-exist and work together in modern CPU architecture? 回答1: You've got it slightly reversed. On every fetch you index into your branch predictor, which tells you whether the instruction that you have just received will be decoded into a taken branch. If not, you fetch the next sequential address. But if your branch predictor says that it will be a taken branch, you don't know which instruction to fetch next, since you haven't decoded this instruction yet. So in order

问题 I've been reading that in most cases (like gcc) the compiler reads the source code in a high level language and spits out the corresponding machine code. Now, machine code by definition is the code that a processor can understand directly. So, machine code should be only machine (processor) dependent and OS independent. But this is not the case. Even if 2 different operating systems are running on the same processor, I can not run the same compiled file (.exe for Windows or .out for Linux) on

问题 I've been reading that in most cases (like gcc) the compiler reads the source code in a high level language and spits out the corresponding machine code. Now, machine code by definition is the code that a processor can understand directly. So, machine code should be only machine (processor) dependent and OS independent. But this is not the case. Even if 2 different operating systems are running on the same processor, I can not run the same compiled file (.exe for Windows or .out for Linux) on