Hi, Given we are coming up close to the freeze, I think this may be a good time to look in to optimizations. I propose we spend some time trying different compilers and profiling Wine under different usage patterns to see what type of speedup we can get. I'm going to see if its possible to compile Wine with LLVM and I think it would be a good idea if someone with an ICC license gave it another shot. Also any gentoo users lurking, now would be a good time to go crazy with your compiler flags, run some benchmarks and file bug reports.
Steven Edwards wrote:
Hi, Given we are coming up close to the freeze, I think this may be a good time to look in to optimizations. I propose we spend some time trying different compilers and profiling Wine under different usage patterns to see what type of speedup we can get. I'm going to see if its possible to compile Wine with LLVM and I think it would be a good idea if someone with an ICC license gave it another shot. Also any gentoo users lurking, now would be a good time to go crazy with your compiler flags, run some benchmarks and file bug reports.
I'd settle for someone telling me which GCC version to use. If you are doing optimization testing, please make sure to test that copy protection hasn't broken as well :)
Thanks, Scott Ritchie
On Tue, Apr 8, 2008 at 4:19 PM, Scott Ritchie scott@open-vote.org wrote:
I'd settle for someone telling me which GCC version to use. If you are doing optimization testing, please make sure to test that copy protection hasn't broken as well :)
Good point. I just tested LLVM 2.2 on OS X and it produces a totally broken Wine so thats out. I see ICC has an eval version for OS X so I am going to give it a shot next.
"Steven Edwards" winehacker@gmail.com wrote:
Good point. I just tested LLVM 2.2 on OS X and it produces a totally broken Wine so thats out. I see ICC has an eval version for OS X so I am going to give it a shot next.
Why not start with Linux first? In that case you have much more helping hands if you are in trouble, you avoid Mac specific code paths that may distort the picture, and Linux has oprofile - unbeatable choice.
On Tue, Apr 8, 2008 at 9:26 PM, Dmitry Timoshkov dmitry@codeweavers.com wrote:
Why not start with Linux first? In that case you have much more helping hands if you are in trouble, you avoid Mac specific code paths that may distort the picture, and Linux has oprofile - unbeatable choice.
I have a 64bit linux host and using -m32 with llvmgcc does not seem to be very well documented. I expect to have problems with icc on x86-64 also. Preconfigured LLVM packages for 2.2 work out of the box on OS X where the current Ubuntu binary is at like 1.7 which does not support inline asm. Don't worry, I'll try it in a 32bit linux vm with my own build of llvm trunk and icc when I have more time.
On Tue, Apr 8, 2008 at 10:54 PM, Steven Edwards winehacker@gmail.com wrote:
I have a 64bit linux host and using -m32 with llvmgcc does not seem to be very well documented. I expect to have problems with icc on x86-64 also. Preconfigured LLVM packages for 2.2 work out of the box on OS X where the current Ubuntu binary is at like 1.7 which does not support inline asm. Don't worry, I'll try it in a 32bit linux vm with my own build of llvm trunk and icc when I have more time.
I wasted a bit more time on this than I should have but I was able to get the 32bit icc to work on my 64bit host to compile Wine with a few hacks. I've documented the process on the wiki and submitted Wine test results. If anyone else has time, please try icc on a 32bit host and let me know if you get a crash when compiling oleaut32. Later when I have more time I am going to run some benchmarks comparing a directx game under wine compiled with gcc and icc.
-
Dmitry Timoshkov -
Scott Ritchie -
Steven Edwards