[Mylo]

I was playing around with pointers and decided to see how big a pointer was. It seemed the pointer was 4 bytes in size, 32 bits. However, I have 8GB Ram, which comes to 2^36 bits. So wouldn't the pointer need at least be 36 bits to address all possible addresses?

#include <iostream>

using std::cout;
using std::endl;

int main()
{
	long long  myVar = 0;
	long long* myPointer = &myVar;

	cout << sizeof(myVar) << endl;     // 8
	cout << sizeof(myPointer) << endl; // 4

	cout << endl << endl;
	system("pause");
	return 0;
}

This post has been edited by Mylo: 03 January 2013 - 04:38 AM

[AKMafia001]

Pointers are 2 bytes on 16-bit systems, 4 on 32-bit, and 8 bytes on 64-bit systems...

I think that depends on the word size of a machine...

[sepp2k]

Mylo, on 03 January 2013 - 09:03 AM, said:

I was playing around with pointers and decided to see how big a pointer was. It seemed the pointer was 4 bytes in size, 32 bits.

This means that you're compiling your application as a 32-bit application.

Quote

However, I have 8GB Ram, which comes to 2^36 bits. So wouldn't the pointer need at least be 36 bits to address all possible addresses?

Yes, it would. 32-bit applications can't use more than 4 GB of RAM.

[Mylo]

Thanks, I didn't know about that. Coming from a java background, C++ is just so much more complicated that I don't even know how to describe it

[sepp2k]

That's not specific to C++. If you're using a 32-bit JVM, you won't be able to use more than 4GB of memory in Java either.

[Mylo]

Yeh, I was more referring to the fact that I actually have to now consider data type sizes for various platforms, and various compiler options, and knowing what each compiler supports (though I'll probably stick to VS) whereas that was close to non existent. But it will definitely improve my understanding of underlying concepts much further.

[Aphex19]

On a related note, your programs don't address memory physically, but virtually. This means that your programs can always see the full address space (either 2^32 or 2^64 bytes), and any address range within that space can be mapped to a physical address, which would indeed be limited to the amount of physical memory installed. If you want to know more, it's worth looking up the details of memory translation mechanism used in x86 (paging).

[ishkabible]

Quote

which would indeed be limited to the amount of physical memory installed

virtual memory, paging, and segfaults actually allow for pages to be stored on the hard drive temporarily. when the program attempts to use a page it's not assigned a segfault is triggered. the OS can first check to see if it stored that on page on the hard drive and swap out some pages then let the program go back to functioning normally. so actually, it's more limited to hard drive space then anything. this is also why windows guarantees 32-bit applications 2 GB of ram and 64-bit applications 2 TB of ram if there is available hard drive space.