I'm running Windows 7, 64-bit, on a 64-bit machine of course.
I'm tried using both Code::Blocks + the Borland 5.5 free compiler, and also CodeLite + GNU g++ compiler.
This is the code I have written to run the test:
Code:const short BITS_PER_BYTE = 8; const short BYTES_PER_ADDRESS = sizeof( void* ); const short MEMORY_SLOT_SIZE = (BYTES_PER_ADDRESS * BITS_PER_BYTE); cout << "Size: " << MEMORY_SLOT_SIZE << "bit" << endl;
Running under 64-bit windows on 64-bit hardware is not all there is to it. 32-bit programs, including 32-bit compilers, can mostly run on a 64-bit system. If your compiler is 32-bit, it will produce 32-bit executables, regardless of whether it is executed on a 64-bit system.
The Borland 5.5 free compiler is 32-bit.
GNU compilers (gcc - for GNU compiler collection) can be built for 32-bit or 64-bit targets, although support for 64-bit targets is a little patchy. If you have obtained executables built for a 32-bit target, it will produce 32-bit code. The two most commonly used windows versions of gcc are Cygwin and mingw, and both are only released in a 32-bit version (IIRC a 64-bit version of mingw is under development, currently about beta status, but I haven't checked for a while). The CodeLite IDE is currently distributed with a mingw 32-bit compiler (or no compiler).
You could have worked all this out by reading the respective documentation (for Borland 5.5, mingw, or even for the CodeLite IDE).
Thanks for your help.Originally Posted by grumpy
Regarding the last bit of advice, I'm sure you're right. However, it would probably have taken a lot longer. For one, I didn't even know where to start looking (I didn't realise the compiler was the cause, although I thought it may have been).
Thanks again.
If you are going to assume your time is more valuable than that of other members here, you will find few people willing to help. Yes, people here are volunteers, but volunteers are a special breed - act as if their time is less valuable than your own, or is something you can tap into when you're too lazy to work for yourself, and they become less willing to help.
I would also point out that references don't really have a size.
I.e. if you have char &x; then sizeof(x) is sizeof(char), and using &x anywhere gives you a pointer so it's sizeof(char*).
Edit: Okay so you can put one inside a struct and then check the struct size.
Last edited by iMalc; 11-06-2012 at 12:30 PM.
My homepage
Advice: Take only as directed - If symptoms persist, please see your debugger
Linus Torvalds: "But it clearly is the only right way. The fact that everybody else does it some other way only means that they are wrong"
If you are talking about what I think you are talking about, the project hasn't made much progress, and I highly doubt it ever will.IIRC a 64-bit version of mingw is under development, currently about beta status, but I haven't checked for a while
Other sources though have a very capable "MinGW64" distribution of GCC 4.5 and above.
Soma
Well ... sometimes it comes down to "three minutes of your time will save three days of my time". Literally! I've put weeks worth of work - over five hours every day - into learning C++, and that's obviously just a start. I've asked only a handful of questions on these forums. I try and solve the problems myself, but with my limited experience and knowledge that's sometimes a big ask.
Besides that - and with all due respect - I reckon there would be not many questions asked in this forum - or any forum - that are not covered by "documentation somewhere".
I believe I've been quite gracious with those that have been willing to help, including yourself. Thanks for your help and for the detailed response I noticed that you made to my other thread too. It is very much appreciated, believe me!
Last edited by Vic Webster Jnr; 11-06-2012 at 04:49 PM.
