Developing in 32-bit Windows but intended for 64-bit Windows

[cag8f]

I am developing/testing a code on a system running Windows 7 32-bit.  The goal is to eventually build an exe from the code and run it on a system running Windows 7 64-bit.  If I do not have access to a 64-bit system, will I be able to accurately/comprehensively test my code to ensure that it will run properly on the 64-bit system?

For example, is there a way, while testing on my 32-bit system, to somehow mimic the key conditions/characteristics of a 64-bit system? Or is there a way that I can build my code/exe in the 32-bit environment, and somehow instruct it to run "in a 32-bit manner" (whatever that means), even if on a 64-bit system?

This may be more of a Windows question, but I decided to start here.

[PainTain]

Simply: No.

Instructions encoded for AMD64/Intel 64 cannot run on a IA-32 processor. Other way round is possible.

This means you can build your script just for 32-bit Windows' and also deploy it for 64-bit machines.

(Although your script should perform the same on both, 32-bit and 64-bit Windows'. (Excluding code which uses the Registry/Inline Assembly))

Edited August 16, 2014 by PainTain

[cag8f]

Thanks for the reply.

Instructions encoded for AMD64/Intel 64 cannot run on a IA-32 processor. Other way round is possible.

This means you can build your script just for 32-bit Windows' and also deploy it for 64-bit machines.

 

This sounds like you are saying I *can* accomplish my goal (If I'm understanding this correctly).  Specifically, the second sentence--isn't it saying that I can build (and test) my script in my 32-bit environment, and deploy it on a 64-bit machine without issue?

[PainTain]

Thanks for the reply.

 

This sounds like you are saying I *can* accomplish my goal (If I'm understanding this correctly).  Specifically, the second sentence--isn't it saying that I can build (and test) my script in my 32-bit environment, and deploy it on a 64-bit machine without issue?

Yes.

You can run 32-bit executables without any problem on 64-bit processors.

So you don't have to build a 64-bit version of your script, you can also deploy the 32-bit executable for both.

[cag8f]

Thanks.  But when I click 'Compile,' a window opens up, and one of the options is "Output arch."  There are 2 check boxes here:

Compile X86 version.

Compile X64 version.

How do these fit into our discussion?  Do I need to make sure to check the latter?

[PainTain]

How do these fit into our discussion?  Do I need to make sure to check the latter?

No, don't check the "x64"-box.

This would compile for 64-bit, and since you are unable to test this version, you just need the x86-version

[cag8f]

OK to follow up though, if an EXE compiled for an x86 system will work without issue on an x64 system, why is there a "compile for x64" option?  Just for my edification at this point.

[jchd]

For those who want or need to produce executables aimed to 64-bit OSes exclusively, maybe for instance that they need to use a DLL available only in 64-bit or other good reason.

[corgano]

Or as previously mentioned if the script uses inline assembly, for example: trancexx a while back made an amazing starfield / warp example using assembly in autoit, the assembly was specific to 32 bit computers only.

For 95% of what you do though, compiling in 32bit will be fine

Edited June 24, 2015 by Jon

[cag8f]

Great, thanks guys.  I don't plan on anything too complicated with this project, so I can stick with a 32 bit environment.  But for the future, in case I do want to dabble in higher level 64 bit Autoit programming, is there some official Autoit documentation that describes when/how I need to modify script writing and/or compiling?