In message [EMAIL PROTECTED], Peter Hunnisett
[EMAIL PROTECTED] writes
snip
Yes, if you only consider systems using a recent glibc and a
thread-safe Xlib.
True. But, I guess, we can assume that for Linux-based system,
right?
Probably, yes.
There are people who run libc5 still. My
Note that the X11DRV_CritSection is sometimes implicitly relied
upon to protect things other than the X11 libraries. For example
the use of the large stack is protected only by this critical
section ...
That's exactly what I was afraid of. Now, there are (mainly) two
places where we have
From: "Alexandre Julliard" [EMAIL PROTECTED]
Sure. I am not proposing to drop other systems, but just for my
information, the other systems are AFAIK, FreeBSD and Solaris.
Are you referring to these systems? In any case, for platforms
were we can not do that trick, we are not 100%
"Dimitrie O. Paun" [EMAIL PROTECTED] writes:
Than why do we include the patch altogether? :)))
IIRC, there were still some issues that were being resolved by
that patch, right? (sorry, I tried to find the relevant WWN, but
it's hard without a search engine).
There are libc issues yes, but
There are a 3 places in the DDRAW dll, but most of them are in the
X11DRV. Anyway, in the long term, I hope that (1) there will be no
non-thread-safe Xlibs, and (2) we'll be able to play similar tricks
with other libcs.
I am not sure that
#define LOCK_X11DRV() EnterCriticalSection(
snip
Yes, if you only consider systems using a recent glibc and a
thread-safe Xlib.
True. But, I guess, we can assume that for Linux-based system,
right?
Probably, yes.
There are people who run libc5 still. My personal computer has it still,
but I haven't used it in a bit as it's
"Dimitrie O. Paun" [EMAIL PROTECTED] writes:
Now, AFAICS, Xlib calls are thread
safe from the glibc point of view, but
until the above mentioned patch got
applied, they were not from Wine POV.
However, now that we play nice with
glibc locking, shouldn't the Xlib
calls become thread safe
From: "Alexandre Julliard" [EMAIL PROTECTED]
Yes, if you only consider systems using a recent glibc and a
thread-safe Xlib.
True. But, I guess, we can assume that for Linux-based system,
right?
I doubt you will have much success with a proposal
that we should stop supporting all other
