1
00:00:00,690 --> 00:00:01,180
Hello.

2
00:00:01,230 --> 00:00:02,550
Welcome back.

3
00:00:02,550 --> 00:00:08,010
I'm processors are specifically designed to be small to reduce power consumption and extend battery

4
00:00:08,070 --> 00:00:14,610
operation essentially for applications such as mobile phones and other embedded devices.

5
00:00:14,610 --> 00:00:19,530
Because of this the uncle is not pure risk architecture in some sense.

6
00:00:19,530 --> 00:00:26,910
The strength of the Army Corps is that it does not take the risk concept too far as we know in the devices

7
00:00:26,910 --> 00:00:27,660
we use today.

8
00:00:27,660 --> 00:00:34,890
The key is not just a raw process or speed but the total effective system performance and power consumption.

9
00:00:36,570 --> 00:00:44,270
Arms core competency lies in taking a risk architecture High Court density and part efficiency and putting

10
00:00:44,280 --> 00:00:51,360
it in one process or court density simply means the amount of space that an executable program takes

11
00:00:51,360 --> 00:00:55,470
up in-memory memory high code density means the program takes less space.

12
00:00:55,470 --> 00:01:03,830
This is quite useful for applications that have limited onboard memory such as mobile forms as we mentioned

13
00:01:03,890 --> 00:01:04,420
earlier.

14
00:01:04,460 --> 00:01:10,370
Risk stands for reduced instruction sets and Sisk stands for complex instruction set.

15
00:01:10,370 --> 00:01:17,130
Now let's see the fundamental difference between Cesc and risk as you may know in software development

16
00:01:17,250 --> 00:01:25,110
a compiler compiles the code and it generated binary file is downloaded onto the processor and risk

17
00:01:25,110 --> 00:01:32,500
systems due to its philosophy of simplifying instruction is greater complexity is placed on the compiler.

18
00:01:32,640 --> 00:01:38,210
The compiler has to take the simple instructions and understand the complex functions.

19
00:01:38,220 --> 00:01:45,330
Those instructions are supposed to perform and generate a simple binary file which will be downloaded

20
00:01:45,420 --> 00:01:47,690
onto the process source.

21
00:01:47,730 --> 00:01:55,770
Therefore complexity is placed on the compiler in the risk system insists architecture.

22
00:01:55,830 --> 00:01:58,470
The compiler does minimal work.

23
00:01:58,500 --> 00:02:05,250
Greater complexity is placed on the process or in effect the process or must be designed complex enough

24
00:02:05,250 --> 00:02:09,610
to understand the complex files generated by the compiler.

25
00:02:10,200 --> 00:02:16,440
So this is the fundamental difference between disk and risk let's just give a quick overview of the

26
00:02:16,440 --> 00:02:20,680
main differences between process source and Intel process source.

27
00:02:20,700 --> 00:02:26,910
There are many differences between Intel and actually by the main difference of course is the instruction

28
00:02:26,910 --> 00:02:29,010
set is a risk.

29
00:02:29,100 --> 00:02:35,700
Architecture and Intel esque architecture also in us we shall see later.

30
00:02:35,700 --> 00:02:39,750
Most instructions can be useful Conditional Execution.

31
00:02:39,780 --> 00:02:43,580
The other key difference between the two is the DNS.

32
00:02:43,850 --> 00:02:52,260
As we shall see later Intel uses the little Indian format while armies armies capable of both little

33
00:02:52,260 --> 00:02:52,820
and big.

34
00:02:52,850 --> 00:03:01,020
Indian Indian as basically dictates the the sequential order in which bytes are arranged when stored

35
00:03:01,020 --> 00:03:02,430
in memory.

36
00:03:02,580 --> 00:03:05,610
We shall see how this works when we start writing code.