July 2022 - Wine-devel - list.winehq.org

Re: [PATCH 6/9] mshtml: Implement nextElementSibling for Elements.
by Marvin 26 Jul '22

26 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119732 Your paranoid android. === w10pro64 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w8 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 5/9] mshtml: Implement lastElementChild for Elements.
by Marvin 26 Jul '22

26 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119731 Your paranoid android. === w1064 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 4/9] mshtml: Implement hasAttributeNS for Elements.
by Marvin 26 Jul '22

26 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119730 Your paranoid android. === w10pro64_ar (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 3/9] mshtml: Implement removeAttributeNS for Elements.
by Marvin 26 Jul '22

26 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119729 Your paranoid android. === w1064 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w1064v1809 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v8 3/8] scrrun: Test MoveFolder with already existing destination.
by Marvin 26 Jul '22

26 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119740 Your paranoid android. === w1064v1507 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v8 2/8] scrrun: Check for null and empty arguments in MoveFolder.
by Marvin 26 Jul '22

26 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119739 Your paranoid android. === w864 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w10pro64_ja (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v2 1/1] ntdll: Restore the timezone bias cache.
by Marvin 26 Jul '22

26 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119688 Your paranoid android. === debian11 (32 bit WoW report) === ntdll: change.c:277: Test failed: should be ready

1 0

Re: [PATCH 1/1] ntdll: Restore the timezone bias cache.
by Marvin 26 Jul '22

26 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119676 Your paranoid android. === debian11 (32 bit report) === ntdll: time.c:473: Test failed: got USD bias 180000000000, ntdll bias 18446744073320925184 === debian11 (32 bit Chinese:China report) === ntdll: time.c:473: Test failed: got USD bias 180000000000, ntdll bias 18446744073320925184 === debian11 (32 bit WoW report) === ntdll: time.c:473: Test failed: got USD bias 180000000000, ntdll bias 18446744073320925184

1 0

Re: [Mingw-w64-public] How to fix error with macros in d3d12?
by Zebediah Figura 25 Jul '22

25 Jul '22

(+ wine-devel) On 6/11/22 13:26, LIU Hao wrote: > 在 2022-06-12 01:59, Zebediah Figura 写道: >>> The combination of `extern` with `__gnu_inline__` is necessary to suppress generation of a function >>> body if the attached function could not be inlined when compiling as C99. >> >> Why do we need that? >> > > Otherwise there would be errors about multiple definitions. > > >>> I don't think there is >>> anything we can do with these headers. Perhaps WIDL should not generate `static` for `FORCEINLINE` >>> functions; or, if that is not an option, `static __inline__` might be a better alternative. >> >> Is it legal to use 'static __forceinline' or 'extern __forceinline' with MSVC? If so I imagine we >> should find a solution that allows them. >> > > Yes, unfortunately. I don't think there is a solution. `extern inline` and `inline` are not > equivalent in C. > > Right, so, apparently MSVC treats both "inline" and "__forceinline" as magic bullets—they can both appear with or without 'static' and 'extern'; they'll always generate a function body but can also be defined in multiple source files (in fact, if the definition differs and the functions aren't static, an arbitrary one is picked and no warning is even printed.) And for good measure you can always take the address too. [So as far as I can tell there's no difference between "inline" and "extern inline" as far as MSVC is concerned.] I guess we can't do anything about that without modifying the language. But of course in lieu of that we should probably fix our headers. I see at least three options: (1) Use "FORCEINLINE" instead of "static FORCEINLINE" for these functions. MSVC never uses FORCEINLINE with static or extern, so this would be more consistent. The downside is we'd need to provide import library definitions for all of these functions, though, which seems less than ideal. (Unless combined with option 3 below.) (2) Use "static inline" for COM wrappers. This of course drops the __always_inline__ attribute. I'm inclined to assert that's a non-issue, but then again I never really saw the point of __always_inline__ anyway. [I guess it can be used to force the compiler to inline even when -finline isn't enough, but surely that would never be the case here...] (2b) Or use "static inline __attribute((__always_inline__))", and define a new macro to encapsulate that. (3) Define __forceinline as "static inline" rather than "extern inline". I have to assume there was a reason this wasn't done in the first place, but there's no documentation in the file and I couldn't easily find discussion about it. As far as I can tell this actually matches MSVC almost exactly, except that multiple definitions will be generated if something takes the function address. That is arguably a break in behaviour which is worse than just failing to link, though. I think my preferred solution is 2 (or 2b I guess). I'm planning to send the attached patch to winehq (since we need to sync widl from there), but I'd like to hear some feedback from the mingw-w64 project first. ἔρρωσθε, Zeb

4 4

Re: [PATCH v3 10/10] mshtml: Inform Gecko of progress done via OnProgress.
by Marvin 25 Jul '22

25 Jul '22

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119640 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: events: Timeout

1 0