Murali
BAN USER1. The Intel 80386, also known as the i386, or just 386,
i - intel
3 - 32-bit microprocessor
86 - pentium series
2. x86-64 is an extension of the IA-32 32-bit version of the x86 instruction set.
It supports vastly larger virtual and physical address spaces than are possible on IA-32,
thereby allowing programmers to conveniently work with much larger data sets.
x86-64 also provides 64-bit general purpose registers and numerous other enhancements. The original specification was created by AMD, and has been implemented by AMD, Intel, VIA, and others.
It is fully backwards compatible with 16-bit and 32-bit x86 code
64 bit means the addressing range ie 2^64, as opposed to 2^32 (i386, 486, 586 (pentium etc), 686).
Both Intel and their competitor AMD have both architectures avail.
We are currently in a transition period as 64 bit takes over from 32 bit.
32 bit SW can run on 32 bit or 64 bit HW. 64 bit SW can only run on 64 bit HW.
64 bit systems tend to be a bit faster for 2 reasons:
1. newer (faster) HW
2. wider bandwidth on I/O bus etc.
Not all apps have 64 bit versions. For home use, you won't notice a significant difference, if any.
For commercial/large org scale users, the extra addressing range is mostly of benefit to large DBs eg Oracle. They will notice a difference (assuming fast disks etc).
Some calculations may(!) benefit as well eg academic (research) environment.
3. Yes, in future there are lot of possibility that we will move forward like 128-bit processor.
But it will take so long time to transition from 64-bit to 128-bit .
Basically if the array is not initialized , it will initially contain some garbage value.
So in this case initially :
a[0] = garbage value
a[1] = garbage value
a[2] = garbage value
a[3] = garbage value
a[4] = garbage value
a[5] = garbage value
Then we are allocating
a[0] = 0 and increment the indx value.
Now the value of indx is 1.
we are trying to print the a[1] .
Guess what : it will be garbage only.
a[2] will also be garbage ,
a[3] will also be garbage.
When I have executed the above program I got the following o/p:
a[indx]-858993460
a[indx]-858993460
a[indx]-858993460
-858993460 is garbage value.
Let me know if you have any further clarifications
@all,
It is garbage value only.
When you compile and execute the following program you will get the output as 0.
#include<stdio.h>
int main()
{
int a[5];
printf("The value of array is %d \n",a[1]);
return 0;
}
########################################> ./a.out
The value of array is 0.
To demo this as a garbage value I have executed on Big endian platform.
# ./a.out
The value of array is -17148080
In this case you will get the -17148080 which is a garbage value only.
Can you please explain why we required hash table.? Because we have to check the same sequence is followed immediately or not?
- Murali June 10, 2013