24.4. Types of Instructions

So, now in today’s unit we are going to focus on instruction format, because as I told you this module will mainly deliver or you will be able to understand, basically how to design an instruction given a set of requirements or a set of specification that is the main goal actually.

In this chunk, we discuss the significance of instruction formats in the context of computer architecture. Instruction formats define how the operations of a computer are specified and executed. Understanding how to design an instruction is crucial because it determines how the CPU interprets commands, handles data, and manages various operations. Essentially, it’s about learning the structure needed to convey actions to the hardware correctly.

Think of instruction formats as the recipes for a dish. Just like a recipe provides a step-by-step guide on how to prepare a meal, instruction formats outline how a CPU should execute tasks. Without a proper recipe, it would be challenging to cook a consistent meal, just as a CPU needs a clear format to process instructions correctly.

So, the most fundamental thing even if it’s a non-computer perspective. So, even if I ask you that you have to operate add two numbers. So, this is one of the very basic instruction we do in the low level school days. This is basically an instruction. So, what is the format of an instruction? So, if I order you something. So, I have to tell you, what to do and also I have to tell you on what objects you have to do the operation and where you have to store the result.

This chunk highlights the basic components that make up any instruction: the operation (known as the opcode), the source operands (the data the operation will use), and the destination (where the results will be stored). For example, the operation 'add' specifies what action to perform, the operands tell the CPU which numbers to add, and finally, we must have a location to store the result of this addition.

Imagine asking someone to bake a cake. You tell them, 'Bake a cake using flour and sugar, and place it in the oven'. The 'bake a cake' is the operation (opcode), 'flour and sugar' are your ingredients (operands), and the 'oven' represents where to bake (destination). Just like in cooking, clear instructions are vital for the CPU!

So, basically opcode and source and result operands these are the two very important things. In case of a computer the operands are actually some immediate operations some immediate values which are specified in the instruction or in the more broad terms for the time being you can think that the values of the operands, that is the variables and the values of the variables are stored in some memory.

Operands can be either immediate values, such as a specific number given directly in the instruction, or they can refer to data stored in memory. Understanding how operands work is essential because they influence what data will be used in computations. The instruction set defines how many operands are needed and where to find them.

Consider a scenario where you’re at a grocery store. If you say, 'I want 2 kilograms of apples', the '2 kilograms' is like an immediate value – it is defined and handed over right away. Alternatively, if you say, 'I want the apples from the shelf', that is akin to referring to an operand stored somewhere (the apples on the shelf) instead of stating an exact quantity.

But, when you are thinking over computer prospective or a code prospective, then after one instruction you have to execute another instruction. So, of course, you have to also tell in that instruction that which is the next instruction to be fetched.

This chunk explains that instructions are executed sequentially in a CPU, meaning each instruction must reference the next one. This process allows the CPU to fetch and execute instructions in order, which ensures logical flow. The next instruction can be either the one directly following or can be determined by jumps or branches depending on conditions in the program.

Think about following a set of written driving directions. The first instruction tells you to 'turn left at the next intersection'. After executing that command, you need to reference the next step: 'continue straight for 3 blocks'. Each step builds on the previous one, similar to how a CPU processes the next instruction after completing the current one.

So, in that case the numbers of instructions are much more. So, in that case the number of bits in the opcode will be larger. So, as I given in the example in the summary that depends on the bit size of the opcode of the reference you can decide how many instructions or how many different type of operations are supported.

Instruction length directly correlates with the complexity of the tasks the CPU can perform. The more bits allocated to the opcode, the more various operations can be expressed. For example, a 3-bit opcode can represent 8 different operations, such as addition, subtraction, multiplication, and division, while a larger opcode allows for even more functionality. Below this threshold, you might not have enough unique instructions available for complex programming requirements.

It's similar to an alphabet - the larger your alphabet, the more words and ideas you can express. If you have a 3-letter alphabet, you can create a handful of simple words. However, if you move to a 26-letter alphabet, you can form countless more sophisticated words and concepts, just like how larger opcodes allow a CPU to handle a greater variety of operations.

Then, basically as I told you many times in the last 2, 3 units that basically an instruction is divided basically into three types like: mathematical, arithmetic operation. Then you can have some load store operation and there is read write and there is some logical operation that is jump on 0 jump not on 0 etcetera.

This chunk outlines the broad categories of instructions that exist within a CPU's instruction set. These groups include mathematical instructions (like addition and subtraction), load/store instructions (which manage data movement between memory and registers), and logical operations (which handle conditional logic like comparisons). Each category serves a distinct purpose and can be employed depending on the task the computer is executing.

Think of these categories as different sections in a library. There is a mathematics section for textbooks, a fiction section for stories, and a reference section for encyclopedias. Just like you choose a book based on the topic you need, a programmer chooses specific instruction types based on the tasks they want the CPU to perform.

So, generally write in a mnemonic fashion. So, for ease of representation we do it in a abbreviation form which are mnemonics.

Instructions are often represented using mnemonics for simplicity and readability. Instead of writing complex binary codes, which are difficult for people to understand, programmers use shorter, symbolic names (like ‘ADD’ for addition). This transformation from binary to mnemonics helps improve code clarity and ease of programming.

Consider how we often use shorthand when texting—like 'BRB' for 'Be Right Back'. This takes a complex phrase and makes it simpler and faster to communicate. Similarly, mnemonics simplify the programming process by allowing developers to easily reference longer operations with shorter terms.

So, basically the generic elements of an instruction and its format so, there are some of the very mandatory features or the mandatory part of an instruction; that is, the opcode as we already discussed unless you tell what to do nobody can say that this is an instruction.

This section emphasizes the mandatory features of any instruction format, including the opcode and the structure necessary to accommodate instructions correctly. Every instruction needs at least an opcode to specify what action should occur, thereby enabling the CPU to perform tasks effectively.

Think of a job order form—that form needs a job title (like 'Engineer') at the top. Without that title, neither the employee nor the management would understand what task is expected to be completed. Similarly, every instruction in programming needs an opcode that defines the action that the CPU is to perform.

--