Re: Call for papers - FOSDEM 2013

2012-11-01 Thread Francois Gouget
On Thu, 1 Nov 2012, Jeremy White wrote: [...] > A 'paper' can be a talk you wish to give, or a topic you think we should > discuss. As always, they should be relatively brief, and should > emphasize discussion and collaboration. I think we will want to talk about the new WineTestBot and its futur

Re: WANTED: compiler barrier for use within Wine

2012-11-01 Thread David Laight
On Thu, Nov 01, 2012 at 09:25:53AM +0100, joerg-cyril.hoe...@t-systems.com wrote: > > Background: I want an atomic read of whatever value a single aligned > int (or DOWRD or whatever) currently appears visible to one core. A simple read of a volatile data item will do that. Look at what signal h

Call for papers - FOSDEM 2013

2012-11-01 Thread Jeremy White
Alright folks, We need to put together a schedule for our room at FOSDEM. So I would like to formally 'call for papers' for FOSDEM. Please email suggested topics to winec...@winehq.org, where I'll collate them and piece them into a schedule. A 'paper' can be a talk you wish to give, or a topic

Re: [PATCH 1/3] advapi: Return the current user as the owner of files (resend 4).

2012-11-01 Thread Alexandre Julliard
"Erich E. Hoover" writes: > This particular patch changes the ACL-reported owner of files from the > "world" (S-1-1-0) to the current user (usually S-1-5-21-0-0-0-1000). I'm not sure that's much better. We should try to determine the actual ownership. -- Alexandre Julliard julli...@winehq.org

Re: winhttp: Fix the error returned from WinHttpGetProxyForUrl when autodetection fails.

2012-11-01 Thread Hans Leidekker
On Thu, 2012-11-01 at 14:52 +0100, Marvin wrote: > While running your changed tests on Windows, I think I found new failures. > Being a bot and all I'm not very good at pattern recognition, so I might be > wrong, but could you please double-check? > Full results can be found at > http://testbot.win

Re: winhttp: Fix the error returned from WinHttpGetProxyForUrl when autodetection fails.

2012-11-01 Thread Marvin
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=22654 Your paranoid android

WANTED: compiler barrier for use within Wine

2012-11-01 Thread Joerg-Cyril.Hoehle
Alexandre Julliard wrote: >A critical section doesn't involve the wine server. I simply saw that path: RtlEnterCriticalSection -> RtlpWaitForCriticalSection -> -> wait_semaphore -> fast_wait | NTDLL_wait_for_multiple_objects -> SERVER_START_REQ but I don't like to argue about your server with yo

Re: WANTED: compiler barrier for use within Wine

2012-11-01 Thread Alexandre Julliard
writes: > Alexandre Julliard wrote: >>> 2. I don't want the player to block in a CS. All it needs is to poll >>> dwStatus. >>It wouldn't block if you don't do other things inside the CS. > I don't understand that one. Code in the player like: > EnterCS(wmm->lock); > local = wmm->dwStat

WANTED: compiler barrier for use within Wine

2012-11-01 Thread Joerg-Cyril.Hoehle
Hi, I'm missing a portable compiler barrier for use within Wine. MSVC has _ReadBarrier, _ReadWriteBarrier etc. http://msdn.microsoft.com/en-us/library/f20w0x5e(v=vs.80).aspx GCC has __asm__ __volatile__("":::"memory"); However compilers other than GCC may be used to compile Wine, e.g. I believe