Linked by Thom Holwerda on Tue 8th Jan 2013 23:27 UTC
Permalink for comment 548060
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2011-01-28
WereCatf,
"So, basically you want Wine with machine-code translation. Too bad that it won't happen without Microsoft's help, as even Wine is still riddled with bugs after all these years."
This kind of project seems right up my alley in terms of my interests and abilities. I think it could be done without the need for "wine" at all as long as the ARM opcodes could implement the same calling conventions which exist on x86.
Most code doesn't self modify, and because of that it is possible to recompile the opcodes from one architecture to another architecture, which isn't far off from what qemu does. Inefficiencies arise because different architectures don't have 1 to 1 correspondence between opcodes, producing overhead. However if this were combined with a good code optimiser (like re-purposing the one in gcc or better yet icc), then you might even end up with emulation that can perform better than the original.
Anyone care to offer me a grant? Since I sure wouldn't have time to work on it unless I could drop my ordinary work and pay a babysitter.