search for: getcurrentthread

On Thu, 2019-01-24 at 19:58 +0100, Dimitry Andric via Release-testers wrote: > On 24 Jan 2019, at 01:49, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: > > > > 8.0.0-rc1 was just tagged (from the branch at r351980). > > > > It took a little longer than planned, but it's looking good. > > > > Please run the test

Hello, I would like to ask a question which is not related to wine, but i think that wine developpers could answer it, or maybe help me a bit. I am working on the linux port of a win32 program. This one uses two functions about win32 threads: GetCurrentThread GetThreadTimes I have found in nt2unix an implementation of the first one. But not for the latter. I have seen that 2 years ago, GetThreadTimes have been implemented in wine/scheduler/, but the files of this directory have been removed. So, my questions are : have these functions been implemente...

...the problem by creating a C++ code only Cocoa framework and linking it with WineLib and my application, but surely there is a better solution for this problem... [Question] winbase.h:1608: error: conflicting types for 'GetCurrentProcess' winbase.h:1609: error: conflicting types for 'GetCurrentThread' winbase.h:1877: error: conflicting types for 'LoadResource' wingdi.h:3345: error: conflicting types for 'AnimatePalette' wingdi.h:3440: error: conflicting types for 'EqualRgn' wingdi.h:3452: error: conflicting types for 'FillRgn' wingdi.h:3456: error: conflicti...

On Mon, May 7, 2018 at 12:35 PM Walter Lee <waltl at google.com> wrote: > On Mon, May 7, 2018 at 2:05 PM Kostya Serebryany <kcc at google.com> wrote: > >> >> >>> and GetFakeStackFast. >> >> >> Not sure. Why don't just disable stack-use-after-return? >> > > Yeah originally I was going to do that, but: > I probably

On Mon, May 7, 2018 at 2:05 PM Kostya Serebryany <kcc at google.com> wrote: > > >> and GetFakeStackFast. > > > Not sure. Why don't just disable stack-use-after-return? > Yeah originally I was going to do that, but: 1. We had a stack use-after-return last month that people had to debug by hand. that would have been caught by ASan with stack-use-after-return. So

...e::get_specified implementation. mshtml: Clean up InvokeEx implementation by using get_dispid_type. mshtml: Moved more logic to HTMLStyle_Create. mshtml: Added IHTMLElement2::get_runtimeStyle hackish implementation. mshtml: Added runtimeStyle tests. activdbg.idl: Undef GetCurrentThread macro to avoid collision with interface function declaration. widl: Added an extension that uses inline functions instead of macros for C interface calls. mshtml: Use inline wrappers and fixed found warnings. mshtml: Properly handle NULL VT_DISPATCH refChild in IHTMLDOMNode::inser...

On Wed, Jul 13, 2016 at 04:48:51PM +0200, Sedat Dilek via llvm-dev wrote: > [ CCed all people who were involved in this thread ] > > Hi Tom, > > personally, I am interested to test the prebuilt-toolchains for > Ubuntu/xenial alias 16.04 LTS and Debian/Jessie v8.5.0 AMD64. > The available toolchains are incomplete and thus useless. > > Just as a fact: There is still no