x64 support

Status
Not open for further replies.
A

Automan

New member
Apart installer issues, why has been dropped the x64 support?
Really almost 90% of the PC of the last 3 years are coming out with x64 OS.
I don't know the real performance improvement between 32bit and 64bit, but running x86 executables under x64 OS is like using an emulator
I'm a bit disappointed about that and i hope in another solution :-)
 
>but running x86 executables under x64 OS is like using an emulator
that is false, there is no performance impact in using x86 the CPU is switching into x86 mode and executing the code nativly.

The support for the x64 bit version was dropped because MS VS 2012 displayed some issues when compiling x64 binary (like arbitrary reordering function calls in argument lists, etc...).
With SP3 thats supposed to have been fixed but for now i don't see a reason to risk strange problems again.

David X.
 
Well, according to official Microsoft reference, the WOV64 subsystem is declared as emulation layer with very little performance loss.
Anyway I think that you can provide with minimal effort a 64bit compiled version along with every new 32bit exe, stating that it is not officially supported. This is just my opinion...
I have 2 PC one desktop with Windows 8.1 OS and the laptop with Windows 7 64.
 
You will not notice any relevant difference running it on 32 bit system or under wow64 process.

Ok, the new PCs come out with 64bit system but where is the 64bit software ? All the software that the "medium user" want is still 32 bit. And the % of old PCs with 32 bit system is still very high.

And do you know why a lot of software are not avaible in x64 ? Because there are not real benefits , the x64 bit processor is more accurate, not faster as the majority of people think. For example in a p2p software there will be not any relevant different using it with 32 or 64 bit instruction, there could be instead new issues in the 64 version (and that's what happened to neoloader).
 
The only real benefits if x64 software are:
1. > 2GB memory allocation per process
2. new registers and opcodes that for appropriately optimized software give a substantial speed improvement, but! This mostly aplyes to FPU intensive applications, a.k.a. multimedia, simulations and scientific applications that do vectorisable operations.

NeoLoader is not such an application, its only part that would benefit from this improvements would be the Hashing and Crypto, but! Its already fast enough and I am not going to change the implementations on my own, its much to easy to fuck something up there and compromise security or cause data corruption, I'll stick to a tested well known library.

And now the downsides:
1. every pointer is twice in size, a.k.a. more memory usage

David X.
 
Status
Not open for further replies.
Back
Top