Harley Laue wrote: > On Mon, May 17, 2010 at 11:17 AM, Doug Winger <justd...@socal.rr.com> wrote: > >> Sorry, I don't understand. Why would you want to run ioq3 in wine?
I don't have 64bit Windows so I asked Marcus whether it's possible to test the ioq3 installers with Wine instead. 64bit Wine is in an early stage of development and far from complete though. So instead of testing ioq3 with Wine it's now the other way around. > The question should have really been: "Is this to fix a bug in > ioquake3 (that may unreliably manifest itself in the native client) or > is this to work around a bug in Wine?" If it's the latter, then I'd > say it may have been unwise to accept/apply the patch. If it was the > former, then this is really a non-issue for debate. Both :-) OP_BLOCK_COPY doesn't take care of stack alignment when calling memcpy. The current 'fix' is likely insufficient though. OTOH Wine's memcpy is probably buggy too as it calls glibc memcpy which could be problematic e.g. due to different calling conventions wrt saving xmm registers. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) _______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
