Thank you all for your interest in this course. I would like to remind the viewers about the purpose of this lecture. I have mentioned this aspect a couple of times in the introductory lecture but it is worth spelling out explicitly in written form. DISCLAIMER: The lecture is meant to give you some familiarity with Microprocessor assembly language, specifically the x86 instruction set. This can be a separate course on its own which is indeed the case in the B.Tech/ B.E curriculum. These lectures are meant for someone who is already familiar with an alternate assembly language but may not know the x86 instructions. So DO NOT use these lectures as a substitute for information regarding the x86 instruction set. I have deliberately kept away from the in-depth details of the instruction and pathological cases as I believe they hinder the learning objectives of this course. I do not claim to be an expert in the x86 assembly language either. You are advised to take the essence of the instruction from this video and refer the textbook by Barry Brey for further details. However, what I cover in this lecture is more than enough to take you through this course. Enjoy your learning experience.
He meant (most likely, and according to logic of things as I see it [not an expert in subject]) that content (an actual held values) of memory slots to which DI and SI point to (because DI and SI are pointers, remember that) will not be anyhow themselves changed/messed up by CMPS, so its safe to use CMPS in relation to original data. DI and SI themselves have to be naturally changed, because you don't want 100 times make the same comparison of one selected pair of memory slots; you want to make 100 times a unique pair comparisons. In other words, you don't want CPU do execute 100 times an operation "compare content of Area Nr.1 with content of Area Nr.B"; instead you want (as intended in example) CPU to execute in chain of 100 tries an "compare content of Area Nr.1 with content of Area Nr.B" "compare content of Area Nr.2 with content of Area Nr.B+1" "compare content of Area Nr.3 with content of Area Nr.B+2" ... .... DI and SI values are like those describing an Area numbers: Area Nr.[DI goes here] and Area Nr.[SI goes here] The contents of respective areas (your original data) do not changes during all that. So that is what he meant most likely (and logically, again).
Thank you all for your interest in this course. I would like to remind the viewers about the purpose of this lecture. I have mentioned this aspect a couple of times in the introductory lecture but it is worth spelling out explicitly in written form.
DISCLAIMER: The lecture is meant to give you some familiarity with Microprocessor assembly language, specifically the x86 instruction set. This can be a separate course on its own which is indeed the case in the B.Tech/ B.E curriculum. These lectures are meant for someone who is already familiar with an alternate assembly language but may not know the x86 instructions. So DO NOT use these lectures as a substitute for information regarding the x86 instruction set. I have deliberately kept away from the in-depth details of the instruction and pathological cases as I believe they hinder the learning objectives of this course. I do not claim to be an expert in the x86 assembly language either. You are advised to take the essence of the instruction from this video and refer the textbook by Barry Brey for further details. However, what I cover in this lecture is more than enough to take you through this course. Enjoy your learning experience.
thank you very good content
Great sir. But if you provide us notes than it will save our lot of time. Because making notes is very big overhead for us.🙏🙏🙏🙏🙏
Sir I have a doubt please help!
here you said while using CMPS operation that only flag is affected. But while doing the operation DI
He meant (most likely, and according to logic of things as I see it [not an expert in subject]) that content (an actual held values) of memory slots to which DI and SI point to (because DI and SI are pointers, remember that) will not be anyhow themselves changed/messed up by CMPS, so its safe to use CMPS in relation to original data. DI and SI themselves have to be naturally changed, because you don't want 100 times make the same comparison of one selected pair of memory slots; you want to make 100 times a unique pair comparisons. In other words, you don't want CPU do execute 100 times an operation "compare content of Area Nr.1 with content of Area Nr.B"; instead you want (as intended in example) CPU to execute in chain of 100 tries an
"compare content of Area Nr.1 with content of Area Nr.B"
"compare content of Area Nr.2 with content of Area Nr.B+1"
"compare content of Area Nr.3 with content of Area Nr.B+2" ...
....
DI and SI values are like those describing an Area numbers: Area Nr.[DI goes here] and Area Nr.[SI goes here]
The contents of respective areas (your original data) do not changes during all that. So that is what he meant most likely (and logically, again).
Data contents in source and destination locns are not modified. Pointers to data are modified (i.e, SI and DI), but that's an internal operation.
thank you very good content